Zapier Integration Quickstart

Use our Zapier integration to easily synchronize registration data with our platform.  Not only would this take out a manual step by eliminating the need to manually add or upload registration data, it also greatly improves the user experience and onboarding flow for new users!

With the Zapier integration enabled new registrations will be synchronized and invited to your event in near real-time. 

General Setup

To use this integration you need a Zapier account. Free accounts can be used for most datasources but Zapier may charge for some specific integration sceanrios.

Crate a Zapier account first on zapier.com.

Once you have created a Zapier account you'd need to create a 'Zap'. A zap connects a trigger with an action. The trigger is typically something you want to listen to, such as a new row being added in a spreadsheet, or a new survey submission. The action defines what you want to happen for each trigger. There is only one option here: sync the registration record with our platform.

Example of such a zap:

Trigger configuration

When you expand the trigger you'd need to authorize Zapier to access your data source. Once that is verified you can test the connection to make sure Zapier can read the data in your file. It's best practice to have at least one row (or record) with your own data prepared in the file so that you can use that during the testing and mapping.

Action configuration

Once the trigger is configured you need to connect with your event on CorporateFitness.app and map each field from the data source on the registration fields.

To authorize you need to enter the 'API key' from your event. You can find this on the Integrations page in the Event Manager section of our platform. Once that is entered and verified you can save this for later re-use and continue with the mapping.

With the mapping you can map each field from your data source to a registration field. You first need to select the event you want to sync with and then select the fields you want to map.

Please note that most fields are optional. Only the 'Code' field is required. You can map this either to a column in your data source like 'employee id' or 'registration id' or use the 'Row ID' option. Once you have mapped all fields from your data source you can continue to test the integration.

Please note that this will actually take your test record and add it to your event. We advise to complete a test to ensure all mappings are configured correctly, but you can skip this if you don't want your test record to be part of the event.

Example Integrations

Here are a few common scenarios but many more integrations are possible:

• Microsoft Excel file (as part of O365)
• Google Sheet
• Google Forms