Resources · Make integration

Swoogo Make integrationAutomate Swoogo with Make.

Every new sign-up in Swoogo can start work in your other tools. The Swoogo Make integration offers 5 modules: 1 instant trigger, 2 actions and 2 searches. This guide is for event teams who build their own automations: connect your account, then build a first scenario step by step.

Try the Swoogo integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Swoogo Make integration do for your events?

The Swoogo Make integration links your Swoogo account to Make, a no-code tool where you build a scenario: a chain of modules that runs on its own. Each module is one brick, such as a trigger that starts the flow or an action that fetches data. With Swoogo, the flow can start the moment a registrant is added, changed or removed, then pass that person on to your CRM, a sheet or a chat channel.

A registrant record that follows every sign-up. Watch Registrants starts the scenario, Get a Registrant pulls the full record, and the next module writes it into the CRM your sales team already uses.

A clean attendee export whenever you need one. List Registrants returns everyone registered for one event, one bundle per person (a bundle is one item passed from a module to the next), ready to fill a spreadsheet before the doors open.

A discount code review. List Discount Codes gives the codes set up for an event, so a marketing lead can review the promotions without logging into Swoogo.

The list stops there: no listed module creates or edits a registrant. For anything else the Swoogo API offers, Make an API Call reuses the same connection. Before picking a tool, the n8n vs Make comparison lays out the differences, the Make pricing page explains how operations are counted, and the Make review gives an overall view of the tool.

Connect

How do you connect Swoogo to Make?

  1. 01

    Copy your API credentials in Swoogo

    In Swoogo, open My Profile, then API Credentials. Copy the Client ID and the Client secret shown on screen. The Make documentation asks for an active Swoogo account with API credentials.

  2. 02

    Add a Swoogo module and create the connection

    In your scenario, add any Swoogo module and click Create a connection. A connection is your Swoogo account linked to Make once, then reused by every Swoogo module. The Connection name field is optional, but a clear name helps later.

  3. 03

    Paste the credentials and confirm

    Paste the Client ID and Client secret you copied, or follow the instructions Make shows on screen, then confirm. Once the connection works, Make lists what it can read from Swoogo while you fill in the module.

First scenario

Your first scenario: from a registrant change to a full record

GoalWhen a registrant is added, updated or removed in Swoogo, Make fetches the complete record of that person for the next step.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the + to place the first module. Everything you add afterwards hangs off this starting point.

  2. 02

    Add Watch Registrants

    Search for Swoogo, pick Watch Registrants, click Create a webhook, then Create a connection with the Client ID and Client secret from your Swoogo profile.

  3. 03

    Fill in the trigger

    Fill in the module fields. Once the connection exists, Make lists the Swoogo items it can read, so you choose from a list instead of typing values by hand.

  4. 04

    Add Get a Registrant

    Click the + on the right of the trigger, add Get a Registrant and map the registrant delivered by the trigger into it. The action returns the full details of that person.

  5. 05

    Test with Run once

    Click Run once, then add or edit a test registrant in Swoogo. Read the bundles each module received and check that the record matches the person you changed.

  6. 06

    Switch the scenario on

    Switch the scenario on. Watch Registrants is instant: Swoogo calls Make through a webhook as soon as a registrant changes, so each change starts a new run of the scenario.

Triggers

What starts a Swoogo scenario?

1 module starts a scenario when something happens in Swoogo. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Swoogo as soon as it happens.

Swoogo1Watch Registrants

Watch Registrants

Instant trigger

In Make“Triggers when a registrant is added, updated, or removed.”

Watch Registrants hands your scenario each registrant who joins, changes or leaves an event, so follow-up work starts without anyone exporting a list from Swoogo.

How it fires
instant. Swoogo calls Make through a webhook as soon as the change happens, which is why Make asks you to create a webhook before the connection.
When to use it
whenever a sign-up should update your CRM, a shared sheet or a team channel, and waiting for someone to check Swoogo by hand is not an option.
Watch out
the same trigger covers additions, updates and removals, so a cancellation reaches your next modules too. Keep that in mind before sending anything to the attendee.
Modules

What else can Swoogo do in Make?

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

Swoogo1

Get a Registrant

Action

In Make“Returns details for a given registrant.”

Get a Registrant returns the full details of one registrant, which gives the next module everything it needs about that person in a single step.

When to use it
right after Watch Registrants, or after any module that points to a registrant, when you want the complete record in hand before writing it elsewhere.
Watch out
it works on one registrant at a time; to go through a whole event, List Registrants is the better pick.
Swoogo2

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call lets you reach any endpoint of the Swoogo API from your scenario, with the connection you already created, so the other four modules are not the limit.

When to use it
when your idea needs an action that none of the listed Swoogo modules offers.
Watch out
this is the most technical module of the list, since you build the request yourself from the Swoogo API documentation.
Swoogo3

List Discount Codes

Search

In Make“Lists all discount codes for a given event.”

List Discount Codes gives you every discount code set up for the event you pick, one bundle per code, so promotions can be reviewed outside Swoogo.

When to use it
before a campaign goes out, to copy the codes of an event into a sheet the marketing team can read.
Watch out
like any search, it can return zero, one or many bundles, and each bundle runs the next modules once. Each of those runs is an operation, the unit Make counts on your plan.
Swoogo4

List Registrants

Search

In Make“Lists all registrants for a given event.”

List Registrants pulls everyone registered for one event, which turns an attendee list into data your other apps can use.

When to use it
for a one-off sync, for example loading the attendees of an event into a badge printing tool or a check-in sheet.
Watch out
a large event means many bundles, and every module placed after it runs once per registrant, so the operations add up quickly.
Need help

Need help automating Swoogo with Make?

A person reads every message.

FAQ

Swoogo and Make: common questions

01Is the Swoogo Make integration free?
Yes, Swoogo is a standard app in Make, so its modules work on the Free plan. The Free plan allows 2 active scenarios, a minimum of 15 minutes between two 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) bring the interval down to 1 minute, remove the cap on active scenarios and count usage in credits each month. Your Swoogo subscription is separate: an active Swoogo account with API credentials is still required.
02What is needed to connect Swoogo to Make?
An active Swoogo account with API credentials, plus a Make account. In Swoogo, open your profile, then API Credentials, and copy the Client ID and the Client secret. In Make, add a Swoogo module, click Create a connection, name it if you like, and paste both values or follow the on-screen instructions. For Watch Registrants, which is instant, click Create a webhook first and then Create a connection. The connection is saved once and reused by every Swoogo module.
03Does the Swoogo trigger in Make react in real time?
Yes. Watch Registrants is an instant trigger: Swoogo calls Make through a webhook as soon as a registrant is added, updated or removed, and the scenario starts on that event. A scheduled trigger works differently, since Make checks it at intervals, every 15 minutes by default on a new scenario. The four other Swoogo modules never start a scenario on their own: List Registrants, List Discount Codes, Get a Registrant and Make an API Call run when an earlier module reaches them.
04What if a Swoogo module is missing in Make?
Use Make an API Call. It calls any endpoint of the Swoogo API with the connection you already have, so the 5 listed modules are not a hard ceiling. The Swoogo list is short: one trigger, two actions (Get a Registrant and Make an API Call) and two searches (List Registrants and List Discount Codes). Nothing in it creates or edits a registrant, so that kind of task goes through the API call. The Make documentation for Swoogo lists no specific limit, and it warns that its content is AI-generated from the Swoogo documentation, so check important details with Swoogo.
05Make or n8n for Swoogo?
It depends on your criteria, not on a ranking. On Make, Swoogo comes with 5 ready-made modules, an instant trigger for registrant changes and the Make an API Call module for the rest, all available from the Free plan. n8n often has a node for the same app, so check whether Swoogo is covered there before deciding. The useful questions are which tool your team already works in, whether the ready-made modules match the scenario you have in mind, and how each tool counts usage on the plan you would pick.
Same platform

Other docs you might need on this stack.

Browse all integrations