Power Automate and Zapier

#What they can do

Both platforms use the same REST API and the same keys as your own code.

Triggers, each a subscription the platform makes for itself: a registration is created, changed or cancelled; an attendee deletes their data; somebody checks in; an order is paid; a lead is captured; a rating is given; a certificate is issued; session slides are published; a hotel stay, a guest's travel, an expense claim or a volunteer's shift changes; somebody joins or leaves a community.

Actions: list events and attendees, find an attendee by email, register somebody with a free ticket (with answers to the event's own questions, as fields), cancel a ticket, check somebody in, list orders, door scans, leads, ticket types, sessions, speakers and sponsors, read an event's statistics and its sales pace, read the door counts, create a discount code and change a ticket type's capacity.

#A key for the platform

In the workspace, Integrations › API & MCP › New key, start from Power Automate or Zapier: events, tickets, orders, attendees (read and change), check-in (read and change), the programme, sponsors, webhooks (change, which is what subscribing needs) and personal data. Take away what your flows do not need: a flow that only posts new registrations to Teams needs attendees:read, people:read and webhooks:write.

What a trigger delivers is what the key could read by polling, so subscribing to attendee.registered needs attendees:read and people:read; the table in Webhooks says what each type needs.

#Power Automate

The AttendBeacon connector is made from the API's own description, so it never drifts from it, and it is on its way to Microsoft's certification. Until it is listed in Power Automate:

1. Ask AttendBeacon support for the connector package (its definition, settings and icon), and import it with pac connector create, as its README describes. This gives you the triggers and the actions.
2. Or, for the actions alone: Data › Custom connectors › New custom connector › Import an OpenAPI from URL with https://attendbeacon.com/api/v1/swagger.json, the API in Swagger 2.0 as custom connectors need. Under Security choose API Key, name X-Api-Key, location Header.
3. Make a connection with your key; the triggers and actions appear under AttendBeacon.

The connector's triggers send X-AttendBeacon-Client: powerautomate, so the workspace labels their subscriptions Power Automate. When a flow is switched off, Power Automate removes its subscription; a subscription whose callback answers 410 Gone is removed too.

The connector's dynamic fields read the event's own registration questions, so Register an attendee shows "Dietary needs" or "Company size" as fields, typed as their answers are.

#Zapier

The AttendBeacon app for Zapier connects with an API key, shows the event's questions as fields in Register Attendee, and has the triggers above as instant triggers: Zapier subscribes when a Zap is switched on and unsubscribes when it is switched off. It is being prepared for Zapier's directory. Until it is listed, Zapier's own Webhooks by Zapier works with the API: a Catch Hook trigger whose address you subscribe with POST /hooks, and Custom Request actions with the key in the Authorization header.

#Make, n8n and others

Any platform that can call an HTTP API works: send the key as Authorization: Bearer, and subscribe to events with POST /hooks and the platform's callback address (see CreateHook). The body each delivery carries is plain JSON, { id, type, timestamp, event, attendee, ... }: the signed webhook's data, lifted to the top. Delete the subscription with DELETE on the Location the subscription answered.

#Seeing what they do

Integrations › Webhooks lists the platforms' subscriptions with the platform that made each; Integrations › API & MCP › Activity of keys lists every call their keys made, refusals included. When a flow stops, those two pages say why.