The four guest triggers run when a guest record changes in your event. They are instant and send the guest's details to Zapier.
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)
Your marketing audience stays in sync with your guest list, without exporting and importing contacts.
In This Article
How the Triggers Work
New Guest
Runs when a guest is added to the event:
Added individually in Diobox
Created from a form submission
Created through Zapier or the API
Imported in bulk from a CSV file
A bulk CSV import does not run the Zap once per guest. All guests from the import are sent to Zapier together in a single Zap run.
Updated Guest Details
Runs when any of the following change on an existing guest:
First name, last name, email, phone, company or title
Confirmation Status
Plus-Ones
Check-in status
Changes to a guest's guest lists, seating or notes do not run this trigger.
Updated Guest Confirmation Status
Runs when an existing guest's Confirmation Status changes to Confirmed, Declined, Waitlisted or Unconfirmed.
New guests added with a status, for example imported as Confirmed, do not run this trigger. Use New Guest for new guests.
A status change also runs Updated Guest Details. If you have Zaps on both triggers, both will run.
Deleted Guest
Runs when a guest is removed from the event, individually or in bulk. Use it to remove or archive the matching record in another app.
Build the Example Zap
Every Zap has two parts: a trigger, followed by one or more actions. The trigger defines which data Diobox sends to Zapier. The actions define what happens to that data in your other apps.
Before you begin, create an API key in your event.
To learn more, see: Managing Zapier API Keys
Part 1: Set Up the Trigger
In this part, you connect your event and choose which guest activity starts the Zap.
Step 1.1 – Create a New Zap
In Zapier, click Create → Zaps.
Step 1.2 – Select Diobox and Your Event
App: search for and select Diobox.
Trigger event: select New Guest, Updated Guest Details, Updated Guest Confirmation Status or Deleted Guest. This example uses New Guest.
Account: click Sign in, paste your API key and confirm. The connection is listed under your event's name. If the event is already connected, select it from the list.
Click Continue.
Step 1.3 – Test the Trigger
Click Test trigger. Zapier retrieves recent guests from your event.
Select one and click Continue with selected record.
The event must have at least one guest for the test to return a result. The selected record is used as sample data when you set up your actions.
Part 2: Add Guests to Mailchimp
The Zap now has access to the guest data from Diobox. In this part, you choose what to do with it: select an app and action event, then map Diobox fields to the fields in that app.
Step 2.1 – Set Up Mailchimp
App: select Mailchimp.
Action event: select Add/Update Subscriber.
Account: sign in to your Mailchimp account.
Click Continue.
Step 2.2 – Map Guest Fields to Subscriber Fields
Audience: select the Mailchimp audience.
Subscriber Email: select the Diobox Email field.
First Name, Last Name and other merge fields: select the matching Diobox fields, such as First Name, Last Name and Company.
Only add guests to a marketing list if they have agreed to receive marketing emails.
Click Continue.
Step 2.3 – Test the Action
Click Test step. Zapier sends the sample guest from Step 1.3 to Mailchimp.
Open your Mailchimp audience and confirm that the contact was added with the expected details.
Step 2.4 – Publish the Zap
Click Publish to turn the Zap on.
From now on, the Zap runs automatically each time a guest is added to your event.
Advanced Workflows
After your Zap is running, you can refine it at any time by changing field mappings, adding more actions or adding filters.
More Ways to Use These Triggers
The same trigger works with any app Zapier supports. For example:
CRM sync: create or update a HubSpot or Salesforce contact when a guest is added or updated (New Guest, Updated Guest Details).
Cancellation alerts: notify your team in Slack when a guest declines (Updated Guest Confirmation Status with a filter).
Guest list backup: add each new guest to a Google Sheet (New Guest).
List cleanup: archive the matching contact in your email platform when a guest is removed (Deleted Guest).
Add More Actions
To do more with the same guest, click + below the action to add another step.
For example, you can also create a contact in your CRM or post a message to your team's Slack channel. The number of steps you can add depends on your Zapier plan.
Filtering Guests
To run actions only for certain guests, add a Filter by Zapier step between the trigger and the action. For example:
With Updated Guest Confirmation Status, continue only when RSVP Status is
declinedto notify your team of cancellations.With New Guest, continue only when Unsubscribed is
falsebefore adding guests to a mailing list.
Output Fields
Each Zap run includes the fields below. Most Zaps only need a few of them, such as the guest's name, email and RSVP Status. Additional fields may be added over time.
Guest
Guest ID – unique ID of the guest, used with Update Guest and Find Guest
Guest Public ID – short public ID of the guest
First Name, Last Name, Full Name
Email, Phone, Company, Title
Unsubscribed –
trueif the guest has unsubscribed from event emails
Status
RSVP Status – the guest's Confirmation Status:
confirmed,declined,waitlistedorunconfirmedConfirmed At – date and time in UTC
Checked In –
trueif the guest has checked inCreated At, Updated At – date and time in UTC
Plus-Ones
Is Plus-One –
trueif the guest is a plus-onePrimary Guest ID – for plus-ones only, the Guest ID of the guest who brought them
Event
Event ID, Event Name