Use this article to resolve common issues with Diobox Zaps. For setup instructions, see Diobox + Zapier Integration Guide.
In This Article
Troubleshooting
My Zap Is Not Running
In Zapier, confirm the Zap is published and turned on.
Open Zap History in Zapier to check for errors or filtered runs.
In Diobox, go to Event Settings → Integrations and confirm the API key still exists. Check its Last Used date.
Confirm the change happened in the event the API key belongs to. Activity in other events does not run the Zap.
Confirm the change is covered by the trigger. For example, Updated Guest Details does not run for changes to guest lists, seating or notes.
Zapier Shows an Authentication Error
The API key used by the connection was deleted or is invalid. Create a new key in Diobox, then go to Apps in Zapier, find the Diobox connection for the event and click Reconnect to enter the new key.
My Zap Ran More Times Than Expected
Multi-guest forms: New Form Submission runs once for each guest on the form.
Edited submissions: New Form Submission also runs when a submission is edited, if the trigger is set to New and Edited Submissions.
Repeat check-ins: New Guest Check-In runs for each check-in, including sessions, activities and repeat check-ins.
One Change Ran Two Different Zaps
A Confirmation Status change runs both Updated Guest Details and Updated Guest Confirmation Status. If you only need status changes, turn off the Zap using Updated Guest, or add a filter to it.
Create Guest Added a Duplicate Guest
Create Guest always creates a new guest. Use Find or Create Guest to check for an existing guest by email first.
Frequently Asked Questions
Which Diobox plans include Zapier?
The Zapier integration is available on the Enterprise plan. Account Owners, Account Admins and Event Admins can create and manage API keys.
Why is the API key specific to one event?
For security. A key can access only the event it was created in, so a Zapier connection cannot read or change guests in any other event in your account. If a key is exposed, the impact is limited to that event, and you can revoke it without affecting your other events.
Why can't I see the full API key after creating it?
For security, the full key is shown only once, at creation. Collaborators on the event can see the Integrations page but not the complete key, so a collaborator whose Diobox account is later removed does not retain remote access to the event. If you lose a key, delete it and create a new one.
What happens when I delete an API key?
Access is revoked immediately. Any Zap using that key stops running and shows an authentication error in Zapier. Deleted keys cannot be restored.
Can one Zap work across multiple events?
No. Each Zap uses one Diobox connection, and each connection belongs to one event. To use the same workflow for several events, create a key in each event and make a copy of the Zap for each connection.
How do I tell which Zapier connection belongs to which event?
Each Diobox connection in Zapier is listed under its event's name. In Diobox, give each key a descriptive name and check the Last Used column to see which keys are active.
How quickly do triggers run?
All Diobox triggers are instant. Data is sent to Zapier as soon as the change occurs in your event.
How many Zapier tasks will my Zaps use?
Zapier bills by tasks. Each action step that runs successfully uses one task. Triggers that run once per guest, such as New Form Submission for multi-guest forms or New Guest Check-In at a large event, can use a significant number of tasks. To control usage, add a Filter by Zapier step so the Zap only continues for the records you need.
A bulk CSV import runs New Guest once for the whole import, not once per guest.
Getting Help
For API keys, guest data or trigger behavior, contact Diobox Support using the messenger in the Diobox app.
For building Zaps, Zapier billing or connections to other apps, contact Zapier Support.