Swapcard

Connect AI agents to Swapcard, the event engagement platform. Agents retrieve events and their details, list and look up attendees for CRM syncs, and run arbitrary GraphQL queries against the Event Admin API for anything beyond the dedicated actions.

5 actions API key available

Swapcard website ↗ Platform Documentation ↗ Capability data verified 2026-07-27

Registrations close 48 hours before the flagship event goes live

Get Event pulls the event's live status, dates, and counts of plannings, exhibitors, and speakers

List Attendees pages through the full attendee list with cursor pagination

The agent diffs the attendee list against the CRM to find unsynced registrations and stale records

The event lead reviews the reconciliation plan, especially any records the sync would modify through a GraphQL mutation

Approved changes apply: CRM upserts for new attendees, Run GraphQL Query mutations for corrections on the Swapcard side

The events channel gets the final counts: attendees synced, corrections applied, exceptions held

What This Integration Enables

Swapcard holds the richest version of your event's attendee data, profiles, sessions, exhibitors, engagement, and most teams touch it through a post-event export. That is backwards: the week around the event is when the data is worth the most and the team has the least time to move it by hand. This connector puts the Event Admin GraphQL API inside FlowRunner flows, so the data moves while the event is still a live opportunity rather than a retrospective. - Reconcile event IDs from other systems by loading core event details in one call - Sync attendee profiles with name, email, job title, and organization into CRMs and spreadsheets, with cursor pagination for large events - Look up a specific event or person on demand inside a larger automation - Keep the CRM and the event platform agreeing during the weeks it matters most - Reach exhibitors, plannings, sessions, groups, and every mutation in the schema through the raw GraphQL escape hatch Because the API is GraphQL, every action returns the raw response under data, and agents request exactly the fields they need rather than paging through bloated payloads. The dedicated actions cover the reads every event team runs weekly; the escape hatch means the connector's ceiling is the schema itself, not the action list. That escape hatch reaches create, update, and delete mutations against a live event, which is precisely why FlowRunner pairs it with a [human-in-the-loop](/concepts/human-in-the-loop) gate.

Without FlowRunner

Two lists, neither trusted Registration truth splits between Swapcard and the CRM, and they disagree by Friday

Attendee data arrives after the event The export lands the following week, when the leads are already cold

The API means a GraphQL project Anything beyond the export button needs someone comfortable writing queries by hand

With FlowRunner

One reconciled roster Agents page the attendee list on schedule and keep the CRM in lockstep

Profiles sync while the event runs Name, email, title, and organization land in the pipeline the day people register

The full schema on tap Dedicated actions cover the common reads, and Run GraphQL Query reaches everything else

Use Case Scenarios

Attendees flow into the CRM before the booth conversations happen

Daily during registration season, the agent runs List Attendees, walking pageInfo.endCursor until the list is exhausted, and upserts each person into [HubSpot](/integrations/hubspot) with job title and organization attached. Sales walks into the event knowing who registered yesterday, not who registered as of last month's export. Get Person backfills full detail for any record that arrived incomplete, and the same nightly diff catches profile updates, the attendee who changed companies between registering and arriving, which is exactly the detail a booth conversation should not get wrong.

One portfolio view across every event

The events team runs a dozen events a year. The agent takes the event IDs from the planning tracker, loads them all with List Events in a single call, and writes title, dates, live status, and the plannings, exhibitors, and speakers counts into [Google Sheets](/integrations/google-sheets). The weekly portfolio review reads one sheet, and events drifting behind on exhibitor or speaker counts stand out on sight, weeks before the drift becomes a launch-week problem.

Registrations from outside land inside, with review

Late registrations come through [Typeform](/integrations/typeform) after the main flow closes. The agent validates each response, then stages the attendee-creation mutation for Run GraphQL Query with the exact GraphQL document and variables visible. The event lead approves the batch, the mutations run, and the confirmation posts to [Slack](/integrations/slack). The escape hatch does the work the dedicated actions do not cover, and a person signs off before it writes to a live event. Late registrants get in, the roster stays authoritative, and nobody hand-enters records at midnight before doors open.

Human-in-Loop Highlight

Run GraphQL Query is deliberately unlimited: it executes any query or mutation the Event Admin schema allows, including deletes against attendees, sessions, and groups on an event that is live or about to be. A mutation with the wrong variables does not fail politely; it edits or removes real records that real attendees and exhibitors are counting on during the highest-stakes week the events team has. So FlowRunner draws the line at the operation type. Queries run freely, powering syncs and reports at machine speed. Mutations always stage first: the agent posts the GraphQL document, the variables, and a plain-language summary of what will change to the event lead, and executes only on approval. The person approving sees exactly what will run, not a paraphrase. Reads are the agent's job. Rewriting a live event is a decision with a name attached.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

5 actions

Events

List Events Retrieves multiple events by their IDs in one call, returning title, dates, timezone, live status, and totals for plannings, exhibitors, and speakers. The batch read behind portfolio reporting and cross-system reconciliation.
Get Event Retrieves a single event by ID with its full summary, including a short HTML description and the same core counts. The lookup for flows already holding an event ID.

People

List Attendees Lists an event's people with core profile fields: name, email, job title, organization. Cursor-based pagination via pageInfo.endCursor and a pageSize control make it practical for large events. The backbone of every CRM sync.
Get Person Retrieves one attendee by person ID with their full profile fields. The detail fetch behind enrichment and exception handling.

Advanced

Run GraphQL Query Executes an arbitrary GraphQL query or mutation against the Event Admin API and returns the raw response. Full schema access, exhibitors, plannings, sessions, groups, and all create, update, and delete mutations. The power tool this page's mutation gate supervises, and the reason the connector's ceiling is the schema, not the action list.

Frequently Asked Questions

What can FlowRunner do with Swapcard?

FlowRunner agents can run List Events, Get Event, and List Attendees in Swapcard, plus 2 more actions.

Does connecting Swapcard to FlowRunner require OAuth?

No. Swapcard connects to FlowRunner with an API key, no OAuth flow required.

Can Swapcard trigger a FlowRunner workflow automatically?

Swapcard doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Swapcard

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us