Mark Meetup no-shows after an event

1. On the Meetup event page, select Attendees, or click More and then Manage attendees.
2. Once check-in mode is open, switch to the Not checked in tab, which lists members who RSVPed yes and were never checked in.
3. Hover over each attendee card on the web and pick No show, or Not coming for an absence the member told you about, or Checked in for someone who was there but not scanned.
4. For members you suspect of skipping often, open their profile, click Membership details for your group and read Attendance history, one member at a time.
5. Every Meetup attendee card takes its own click, and it is easy to mark someone No show who messaged you to cancel, which then counts against them in their history.

The workshop ended an hour ago. Mark everyone who was not checked in as a no-show, except Ana and Tom, who told me they were sick.

1. 01

   Wait until the event is over

   The agent finds the event with list_events and does nothing before its end time, because people still arrive late. Check-in data is read only after the event has ended.

2. 02

   Build the absent list

   list_attendees for going and for checked_in gives the two sides; everyone going and not checked in is a candidate. A member who brought guests counts once, by their own check-in.

3. 03

   Separate excused from silent

   Members you name as excused in the prompt are marked not_coming. When a name you mention matches two attendees, the agent asks which one instead of picking.

4. 04

   Mark in one batch, then read it back

   mark_attendance sets no_show for the rest in one call. The agent then reads the attendee list again and repeats the call for anyone whose status did not change.

5. 05

   Point out repeat no-shows

   For each new no-show, the agent checks the no_show lists of your last few past events and names the members who skipped more than once, so you can decide on your group's rule. It does not remove anyone.

Data Workshop, Wed 7 Oct 2026: 32 going, 21 checked in.
2 marked not coming: Ana L., Tom W. (you said they were sick).
9 marked no show. Re-read the list: all 11 changes saved.
Repeat no-shows in the last 4 events: Piotr S. (3 times), Mia K. (2 times).
No one was removed from the group.

• Meetup opens check-in mode 1 hour before the start; QR scanning in the Meetup app stays open until 24 hours after the end, and manual marking stays available after that.
• Meetup separates No show, an absence without notice, from Not coming, an absence the member justified or announced, and both land in the Absent tab.
• Meetup attendance history counts Yes RSVPs, No RSVPs, waitlisted events and No-shows per member, only within your group, and only on the Meetup website.
• Every member of a Meetup leadership team can use check-in, but attendance history is visible to organizers, co-organizers and assistant organizers, not to event organizers.
• Meetup lists a known issue where attendance changes on a past event, such as manually marking a member, sometimes do not save.

mark_attendance changes only your own Meetup data and reach no one else, so it runs without asking first.

Sources: Meetup Help: Manage attendees and track attendance on the web · Meetup Help: New attendee list and QR code check-in · Meetup Help: A member's attendance history · Meetup Help: Managing a leadership team · Meetup Help: Issues when editing an existing event

curl https://cotlet.dev/api/v1/meetup/mark_attendance \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"event_id":"311204587","member_ids":["402118","402119"],"status":"no_show"}'

{
  "event_id": "311204587",
  "updated": 2,
  "status": "no_show"
}

MCP: add https://cotlet.dev/mcp/v1 with the same key; the tool is meetup_mark_attendance. Example data.

• Create a series of Meetup events from an agenda
• Message Meetup event attendees about a last-minute change
• Meetup API and MCP server: every tool
• All use cases