Zapier connects Diobox with thousands of apps, including CRMs, email marketing platforms, spreadsheets and messaging tools, without writing code. Activity in your event can start workflows in other apps, and other apps can create, update or find guests in your event.
Requirements
A Diobox Enterprise plan
An Account Owner, Account Admin or Event Admin role in Diobox
A Zapier account (zapier.com)
The Zapier integration is set up for each event individually, in Event Settings → Integrations.
How Diobox Connects to Zapier
Zapier connects to Diobox using an API key. Each key is created inside a single event and can access only that event's data. A key created for one event cannot read or change guests in any other event in your account.
You can create one or more keys per event, depending on how you want to manage access for each key.
To create a new key, go to: Event Settings → Integrations → click New API Key.
Learn more: Managing Zapier API Keys
How Diobox Works with Zapier
A Zapier workflow is called a Zap. Every Zap starts with a trigger and runs one or more actions. Diobox can be used in a Zap in two ways.
Triggers
A trigger starts a Zap when something happens in your event, such as a guest registering or checking in. All Diobox triggers are instant.
Actions and Searches
Actions and searches run when something happens in another app. Actions create or update guests in Diobox. Searches find existing guests so later steps can use their data.
Guest Triggers
Start a Zap when guests are added, updated or removed.
New Guest – triggers when a guest is added to an event, whether individually, through a form submission or by bulk import.
Updated Guest Details – triggers when a guest's name, email, phone, company or title changes, or when their Confirmation Status, Plus-Ones or check-in status changes.
Updated Guest Confirmation Status – triggers when a guest's Confirmation Status changes to Confirmed, Declined, Waitlisted or Unconfirmed.
Deleted Guest – triggers when a guest is removed from an event, individually or in bulk.
Example Zap: Add New Guests to Mailchimp
When a guest is added to your event (Diobox · New Guest)
Then add them to a Mailchimp audience (Mailchimp · Add/Update Subscriber)
Check-In Trigger
New Guest Check-In triggers when a guest checks in to an event, session or activity, including repeat check-ins.
Example Zap: Post Guest Check-Ins to Slack
When a guest checks in (Diobox · New Guest Check-In)
Then post a message to a Slack channel (Slack · Send Channel Message)
Form Submission Trigger
New Form Submission triggers when an event form (Registration, RSVP, Ticket, Waitlist or Survey) is submitted or edited.
Example Zap: Log Form Submissions in Google Sheets
When an event form is submitted (Diobox · New Form Submission)
Then add a row to a spreadsheet (Google Sheets · Create Spreadsheet Row)
Actions and Searches
Actions and searches let other apps add and update guests in your event. Use them to bring in guests from a CRM, spreadsheet or form tool without importing files manually.
Create Guest – creates a new guest in an event. It always adds a new guest, even if a guest with the same email already exists.
Update Guest – updates an existing guest's details or Confirmation Status. The guest is identified by Guest ID.
Find Guest – finds an existing guest by email or Guest ID and returns the guest's data for later steps.
Find or Create Guest – finds a guest by email, or creates a new guest if none is found. Use it to avoid duplicate guests.
Fields left empty are not changed in Diobox. Changes made through Zapier also run the matching Diobox triggers. For example, Update Guest runs Updated Guest Details, so avoid building two Zaps that update each other in a loop.
Example Zap: Add Guests from a Google Sheet
When a row is added to a spreadsheet (Google Sheets · New Spreadsheet Row)
Then add the guest to your event, unless they already exist (Diobox · Find or Create Guest)
Using Zapier with Multiple Events
Each Diobox connection in Zapier belongs to one event and is listed under that event's name. To run the same workflow for several events, create an API key in each event, connect each one in Zapier and make a copy of the Zap for each connection.