# Mark Meetup no-shows after an event

> After a Meetup event, an agent marks attendees who never checked in as no-show or not coming and lists repeat no-shows from past events.

Source: https://cotlet.dev/integrations/meetup-api-mcp-server/mark-no-shows

The event is over, half the room was checked in by QR code and the rest by memory. Back home you open the Not checked in tab and decide, card by card, who skipped without a word and who wrote that they could not come.

Cotlet does it in your own Meetup account with list\_events, list\_attendees and mark\_attendance, called by your AI agent, an n8n workflow or a script.

[Request access](https://cotlet.dev/app/signup?app=meetup) [All Meetup tools](https://cotlet.dev/integrations/meetup-api-mcp-server)

Hosted · nothing to install or maintain

Official options

## Can Meetup do this on its own?

Meetup has check-in mode with tabs for Checked in, Not checked in and Absent, QR code scanning in the Meetup app and a per-member attendance history (help center checked 12 Oct 2026). The help center describes marking absences one attendee at a time and does not offer a rule such as "everyone not checked in is a no-show". Meetup's API has no call to mark check-ins or no-shows, even on Meetup Pro (checked 11 Oct 2026).

By hand

## How you do it in Meetup today

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.

With an agent

## How to mark Meetup no-shows after an event

Prompt

```
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.

### What you get back

Example data

```
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.
```

### Other ways to ask

- Every Thursday morning, mark no-shows for Wednesday's event and send me only the repeat no-shows.
- Here is the sign-in sheet from the door. Check in everyone on it and mark the rest as no-show.
- List members who were no-shows at two or more of our last five events, without marking anything.
- Mark Ben R. as checked in for last night; he came late and was not scanned.

Before you automate it

## What Meetup allows, and what to know first

- 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](https://help.meetup.com/hc/en-us/articles/9389668230541-Manage-attendees-and-track-attendance-for-your-Meetup-event-on-the-web) · [Meetup Help: New attendee list and QR code check-in](https://help.meetup.com/hc/en-us/articles/45352992737677-Introducing-the-new-attendee-list-and-QR-code-check-in) · [Meetup Help: A member's attendance history](https://help.meetup.com/hc/en-us/articles/42877005264397-How-to-view-a-member-s-attendance-history-in-your-group) · [Meetup Help: Managing a leadership team](https://help.meetup.com/hc/en-us/articles/360002879411-Managing-a-leadership-team) · [Meetup Help: Issues when editing an existing event](https://help.meetup.com/hc/en-us/articles/32274968215437-I-m-having-issues-when-editing-an-existing-event-for-one-of-my-groups)

REST

## Call mark\_attendance from a script

curl

```
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"}'
```

Example response

```
{
"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.

[Schedule it in n8n, Make, Zapier or cron](https://cotlet.dev/integrations/meetup-api-mcp-server#automations)

Tools

## Meetup tools this automation uses

__Cotlet Meetup tools used to mark Meetup no-shows after an event__
| Tool | Parameters |
| ---------------- | ------------------------------------- |
| list\_events | group\_urlname, status, limit, cursor |
| list\_attendees | event\_id, status, cursor |
| mark\_attendance | event\_id, member\_ids, status |

[All 14 Meetup tools with descriptions](https://cotlet.dev/integrations/meetup-api-mcp-server#tools)

## Frequently asked questions

### Do members get told they were marked as a no-show?

Meetup's help center does not describe a notification for this. The mark shows up in the member's attendance history for your group, which your organizers, co-organizers and assistant organizers can read on the website.

## More Meetup automations

- [Create a series of Meetup events from an agenda](https://cotlet.dev/integrations/meetup-api-mcp-server/create-events-from-agenda)
- [Message Meetup event attendees about a last-minute change](https://cotlet.dev/integrations/meetup-api-mcp-server/message-event-attendees)
- [Meetup API and MCP server: every tool](https://cotlet.dev/integrations/meetup-api-mcp-server)
- [All use cases](https://cotlet.dev/use-cases)

## Give your agent access to Meetup.

Free 7-day trial with 5,000 credits, no card needed. Cotlet is independent and not affiliated with Meetup.

[Request access](https://cotlet.dev/app/signup?app=meetup)