Skip to main content
Import Sessions Through Zapier
Ariane Ramirez avatar
Written by Ariane Ramirez
Updated this week

Import Session Information to Accelevents

Aside from uploading sessions through a CSV file, you can import sessions from another platform, such as Airtable or Google Sheets to Accelevents through Zapier integration. You can create a zap that imports sessions to Accelevents when the session is created or updated on the other platform.

Accelevents has an official app published in Zapier for integrating with other platforms. The steps below will show you how to connect your Accelevents account to Zapier and then build your integration between your event and the other apps available in Zapier.

A Zap is like your personal assistant following all your instructions to complete the task. It has two essential components: a trigger and an action. The trigger is an event or condition as to when the action will happen. The action is the command that will complete your goal.

Create a Zap

Click the buttons below to learn how to set up the trigger and action. If the platform you're working with is not in the examples below, you can still follow the same steps as they are mostly the same for every platform.

Airtable + Accelevents

Google Sheets + Accelevents


Session Import and Update Behavior

Below are the expected behavior when you create new sessions or make changes to existing ones after the Zap is turned on

Create New Sessions

  • Newly created sessions from the integrated platform will be imported to Accelevents, as long as the required fields have a valid value (e.g., session date and time are within the event duration, main stage sessions are not overlapping with other main stage sessions)

  • Existing sessions from the integrated platform will only be imported to Accelevents when the record is updated in the other platform.

Update Session Information

  • Sessions will sync if the Session ID matches in the other platform and Accelevents, regardless of where and how the sessions are created. The Session ID allows the integration to update the correct session even if there are sessions with the same name.

  • If the Session ID is removed from the other platform, a new session will be created in Accelevents, instead of updating the existing one.

  • When updates are made in the integrated platform, the new data will sync with Accelevents, replacing the existing data.

  • When updates are made in Accelevents and that field is not mapped in the Zap or is blank in the other platform (e.g. description, session visibility), that field will update to the default session settings (blank description field, the session is visible) if updates are done in the other platform.

  • Deleted Accelevents sessions will reappear in Accelevents if changes are made to the existing session in the integrated platform.

  • Deleted sessions from the integrated platform will not be deleted in Accelevents.

Did this answer your question?