Zapier is a no-code solution, an external tool that connects two apps together. It's compatible with many common tools, but it's recommended to first check on their website to see if the connection with your app is possible.

Below are some tips for connecting Swapcard with another app (when compatible). If you have further questions, please contact the Zapier support team.

What Zapier is not meant for

Connect the second app. You will have to generate an API key from your Swapcard organizer account.

Define the mapping in the action section:

Please note that in Swapcard:

To export data you have different triggers possible:

Note that exporting data can be highly tasks consuming.

Add filtering

If you want to import or export following specific conditions, you can click on the "+" and select Filters. There you can define what is the condition.

If you're using Zapier to automate your workflow, you may have encountered the need to attach a ticket to a person that was added through Zapier. This can be done easily with just a few simple steps.

Before you can attach a ticket to a person, you need to make sure they are already in your contacts. If you have just added them through Zapier, they should already be there. If not, you can manually add them by going to your contacts and clicking on the "Add Contact" button.

Once you have located the person in your contacts, click on their name to open their profile. This will bring up all of their information and any tickets that are currently attached to them.

In the person's profile, you will see a button labeled "Attach Ticket" near the top of the page. Click on this button to begin attaching a ticket to this person.

A pop-up window will appear with a list of all your available tickets. Select the ticket you want to attach to this person and click "Attach".

After selecting the ticket, you will be brought back to the person's profile where you will see the ticket listed under their information. This confirms that the ticket has been successfully attached to this person.

If you are using Swapcard In-App for your event registration, you can easily integrate it with Zapier to automate the process of adding new attendees to your event. This will save you time and effort, and ensure that all your attendee information is accurately captured.

The first step is to make sure that your registration mode is set to In-App registration.

In order for Zapier to assign tickets to new attendees, you will need to create at least one ticket on Swapcard. This can be done in the "Tickets" section of your event dashboard.

Now it's time to head over to Zapier and create a new zap. A zap is a connection between two applications that allows them to communicate with each other.

The trigger is the event that will initiate the zap. In this case, we want the zap to be triggered when a new attendee is added to your event.

Next, you will need to select Swapcard as the application that you want to connect with your trigger application.

Now you will need to select the action that you want Zapier to perform when the trigger event occurs. In this case, we want Zapier to create a new person (attendee) on Swapcard.

In order for Zapier to create a new person on Swapcard, you will need to map all the required fields. These are the fields that are necessary for creating a new person, such as email, first name, last name, and client ID.

Finally, you will need to select the ticket that you want to assign to the new person on Swapcard.

That's it! Your zap is now set up and ready to go. Whenever a new attendee is added to your event, Zapier will automatically create a new person on Swapcard and assign them the selected ticket. This will save you time and ensure that all your attendee information is accurately captured.

If data isn't flowing as expected, work through the checks below in order. Most issues can be resolved without contacting support.

Zaps left in draft or paused state run no actions. Verify that your Zap is active and deployed before investigating anything else.

Even when a Zap is active, Zapier may change or expire its webhook URL without returning an error. To refresh it, disable the Zap, then re-enable it. This forces Zapier to generate a new URL.

API keys are event-specific. Check that:

To create a new key, go to studio.swapcard.com/api-keys and click Create a new key.

The Task History tab in Zapier is the primary diagnostic tool. Open it and look for failed tasks. The table below covers the most common errors:

Before running a bulk import, use Zapier's Test button on the Action step to send one record. Verify the person appears correctly in Swapcard with the right groups, ticket, visibility, and login access.

If data stops mid-import, you may have hit your plan's task limit. Go to Zapier Settings → Usage to check. The free plan allows 100 tasks per month — once the limit is reached, tasks silently stop flowing.

If only some records flow through, a Filter step is often the cause. Filtered records appear in Task History as Filtered, not Errored — easy to miss. Review your Filter step conditions to make sure they match your data.

Use the table below to verify each field is configured correctly before running your Zap.

If none of the steps above resolve the issue, contact the support team with the following information so they can begin their investigation: