Resources · Make integration

Swapcard Make integrationAutomate Swapcard with Make.

Tired of copying attendees into Swapcard by hand? The Swapcard Make integration gives you 8 modules: 2 triggers, 5 actions and 1 search. This guide shows event teams how to link the account, then walks through a first working scenario.

Try the Swapcard integration on MakeSee the 8 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Swapcard Make integration do for you?

The Swapcard Make integration links your Swapcard account to Make, a visual tool where you build a scenario (an automation made of modules, each one a single brick like a trigger, an action or a search). Once linked, Make can spot new events and new attendees in Swapcard and add, change or remove people on an event without any code.

Attendee lists that stay in sync. When someone registers through a form or another tool, Create an Event Person adds them to the right Swapcard event. If their job title changes later, Update an Event Person edits the same record instead of creating a duplicate.

A CRM that knows who showed up on the list. Watch Event People notices each new attendee on the scenario's schedule, and Get an Event Person pulls the full record, so your sales team sees who joined without exporting a file.

Staff added to every new event. Watch Events catches each event your team creates, then Create an Event Person puts your hosts or moderators on it at the next check.

What Make does not do here: both triggers are scheduled, so nothing fires the second a change happens, and there is no Make an API Call module. For anything the ready-made modules miss, Execute a GraphQL Query sends your own request. The Make documentation for this app also warns that its text is AI-generated from Swapcard's docs and may hold mistakes, so double-check anything important. Swapcard may also have a node on n8n; the n8n vs Make comparison helps you decide. New to the editor? The Make training covers the basics, and the Make pricing page explains plans.

Connect

How do you connect Swapcard to Make?

  1. 01

    Generate an API key in Swapcard

    In Swapcard, open the menu in the top-right corner under your name and choose API keys. Click Create a new key, give it a name you will recognize, click Generate the key, then copy the key shown on screen.

  2. 02

    Add a Swapcard module in Make

    Open your scenario in Make, add any Swapcard module and click Create a connection. A connection is your Swapcard account linked to Make once, then reused by every Swapcard module you add later.

  3. 03

    Paste the key and save

    If you like, type a label in Connection name so you can tell accounts apart. Paste the key you copied from Swapcard, or follow the instructions on screen, and save. The module can now read your events.

First scenario

Build your first Swapcard scenario

GoalWhen a new event is created in Swapcard, Make adds your host to its attendee list.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario. The empty editor shows a large +: click it to add the module that will start everything.

  2. 02

    Pick Watch Events

    Search for Swapcard, choose Watch Events and select the connection you made earlier. This trigger looks for events created since the last check.

  3. 03

    Add Create an Event Person

    Click the + on the right of the trigger and pick Create an Event Person. Map the event coming from Watch Events, then fill in your host's details in the fields Make shows.

  4. 04

    Test with Run once

    Create a test event in Swapcard, then click Run once. Each module shows the bundles it received (a bundle is one item passed along, here one event), so you can check the host landed on it.

  5. 05

    Schedule and switch on

    Open the clock on Watch Events: a new scenario checks every 15 minutes by default. Keep that or pick another interval your plan allows, then switch the scenario on.

Triggers

Swapcard triggers in Make

2 modules start a scenario when something happens in Swapcard. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Swapcard as soon as it happens.

Swapcard1Watch Event People

Watch Event People

Scheduled trigger

In Make“Triggers when new event people have been created.”

Hand every new attendee to the rest of your stack without exporting anything: this trigger picks up the people newly created on your Swapcard events and passes each one on as its own bundle, ready for the next module.

How it fires
it is a scheduled trigger, so Make checks Swapcard on the scenario's schedule rather than being alerted the moment a person is added.
When to use it
your sales team wants each new registrant copied into the CRM or a shared sheet.
Watch out
each person Make handles counts as operations on your plan, so a big import in Swapcard means a busy run.
Swapcard2Watch Events

Watch Events

Scheduled trigger

In Make“Triggers when a new event has been created.”

Get a heads-up each time your team sets up a new event in Swapcard, so the follow-up work starts on its own: announcing it, preparing a checklist or adding staff to the attendee list.

How it fires
scheduled; Make asks Swapcard for new events at each run of the scenario, every 15 minutes by default, and never in real time.
When to use it
you run many events and want each new one to kick off the same setup steps.
Watch out
it reacts to creation only, so edits to an existing event will not start the scenario.
Modules

Everything Swapcard can do in Make

Swapcard gives you 6 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Swapcard1

Create an Event Person

Action

In Make“Creates a new person on an specific event.”

Put someone on the attendee list of a chosen Swapcard event without opening the Event Studio. Make adds the person, and the result can flow into the next module.

When to use it
a registration lands in a form, a spreadsheet or your CRM and you want that person on the event right away.
Watch out
if the person may already exist, run Search Event People first to avoid a duplicate.
Swapcard2

Delete an Event Person

Action

In Make“Deletes an event person.”

Take a person off a Swapcard event so your attendee list matches reality after a cancellation or a refund in another tool.

When to use it
someone cancels their ticket elsewhere and should disappear from the event app.
Watch out
a deletion acts on a real attendee, so test it on a dummy attendee with Run once before letting it act on real people.
Swapcard3

Execute a GraphQL Query

Action

In Make“Performs an arbitrary authorized GraphQL query.”

Reach the parts of Swapcard the ready-made modules skip by sending your own GraphQL query through the connection you already set up.

When to use it
you need data or an operation that none of the other seven modules offers, and you or a developer can write the query.
Watch out
this module expects you to know Swapcard's GraphQL schema; Make will not build the query for you, so keep a tested version handy.
Swapcard4

Get an Event Person

Action

In Make“Retrieves an event person.”

Pull the full record of one attendee you already know, so later modules can use their details in an email, a sheet or a CRM entry.

When to use it
after Watch Event People or a search, when you need that single person's complete profile before sending it elsewhere.
Watch out
it returns one person only; to scan a list, reach for Search Event People instead.
Swapcard5

Update an Event Person

Action

In Make“Updates an event person.”

Change the details of an attendee already on a Swapcard event, so the record people see in the event app stays accurate.

When to use it
a contact's company or role changes in your CRM and their Swapcard profile should follow.
Watch out
the module edits an existing person, so find the right one first with Search Event People or Get an Event Person rather than guessing.
Swapcard6

Search Event People

Search

In Make“Searches for event people or lists them all.”

Look up attendees on an event, or list all of them, and hand each match to the next module as a separate bundle.

When to use it
before creating someone, to check whether they are already registered, or to send the whole list to a spreadsheet.
Watch out
a search can return zero, one or many people, and every module after it runs once per person, which adds operations fast.
Need help

Need help automating Swapcard with Make?

A person reads every message.

FAQ

Swapcard and Make: common questions

01Is the Swapcard Make integration free?
Yes, on the Make side. Swapcard is a standard app, so its modules are available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one per module per bundle. You still need your own active Swapcard account, which Swapcard bills separately.
02What do you need to connect Swapcard to Make?
An active Swapcard account and an API key. In Swapcard, open the menu under your name, go to API keys, click Create a new key, name it, generate it and copy it. Then in Make, add any Swapcard module, click Create a connection, optionally name the connection, and paste the key. The access token comes from the Event Studio, so you need access to it on your Swapcard account. Once saved, the same connection works for all 8 Swapcard modules in any scenario you build.
03Do Swapcard triggers in Make work in real time?
No. Both Swapcard triggers, Watch Event People and Watch Events, are scheduled: Make checks Swapcard each time the scenario runs rather than being called by Swapcard. A new scenario runs every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval allowed; paid plans can go down to 1 minute. If a short delay matters for your event, pick the tightest interval your plan offers and keep in mind that each check uses operations.
04What if a Swapcard module you need is missing in Make?
Start with Execute a GraphQL Query. It sends any authorized GraphQL request to Swapcard through your existing connection, which can fill a gap once you know the query you want. There is no Make an API Call module for Swapcard, so do not look for one. If the query route feels too technical, another app in your stack may hold the data you need, or the team behind this site can help you design the scenario during a 60-minute audit.
05Should you use Make or n8n for Swapcard?
It depends on what you need to automate. On Make, Swapcard comes with 8 ready-made modules: 2 scheduled triggers, 5 actions and 1 search, plus a GraphQL module for everything else. If those cover your attendee workflows, Make gives you a visual editor and a guided connection. n8n may also offer a Swapcard node; check which operations it covers before choosing. Compare the modules each tool offers against your real use case rather than picking by reputation.
Same platform

Other docs you might need on this stack.

Browse all integrations