The New Form Submission trigger runs when an event form is submitted or edited. It is instant and sends the guest's details, order details and form answers to Zapier.
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)
Every registration appears in a shared spreadsheet, with each form answer in its own column, ready to sort, filter and share with your team.
This article walks you through building this Zap step by step. The same steps work with any app: replace Google Sheets with the tool your team uses.
In This Article
How the Trigger Works
The Zap runs once for each guest on a form, not once per submission.
For example, a ticket order for three guests runs the Zap three times and adds three rows to a spreadsheet. Each run includes the full order details, such as Order ID and Order Total, so you can link every guest back to the same order.
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 form submissions start 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 Form Submission.
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 – Choose the Event Form
Form: select a form from the list of forms in your event.
If you do not select a form, the Zap runs for submissions to every form in the event.
Submission Type: select New Submissions Only to run the Zap when the form is submitted, or New and Edited Submissions to also run it when an existing submission is edited.
Click Continue.
Step 1.4 – Test the Trigger
Click Test trigger. Zapier retrieves recent submissions for the selected form.
Select one and click Continue with selected record.
The form must have at least one submission for the test to return a result. The selected record is used as sample data when you set up your actions.
Part 2: Add Submissions to Google Sheets
The Zap now has access to the submission 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 Google Sheets
App: select Google Sheets.
Action event: select Create Spreadsheet Row. Google Sheets offers other actions, such as updating an existing row.
Account: sign in to your Google account.
Click Continue.
Step 2.2 – Map Fields to Spreadsheet Columns
Select the destination for the data:
Drive: select My Drive (default) or a shared drive.
Spreadsheet: select the Google Sheet.
Worksheet: select the worksheet (tab) within the spreadsheet.
Zapier then displays a field for each column in the worksheet. For each column, select the Diobox field that should fill it, for example Guest First Name, Guest Email or a specific form question. Each time the Zap runs, Zapier inserts the submission data into the matching columns.
Click Continue.
Step 2.3 – Test the Action
Click Test step. Zapier sends the sample submission from Step 1.4 to Google Sheets.
Open your spreadsheet and confirm that a new row was added with the expected data.
Step 2.4 – Publish the Zap
Click Publish to turn the Zap on.
From now on, the Zap runs automatically for each new submission, and for edited submissions if you selected New and Edited Submissions.
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 This Trigger
The same trigger works with any app Zapier supports. For example:
Registration alerts: post each new registration to a Slack or Microsoft Teams channel, including Answers Summary.
Email marketing: add registrants to a Mailchimp or Klaviyo audience.
CRM: create or update a contact in HubSpot or Salesforce, with form answers mapped to contact properties.
Sales follow-up: notify a team member by email when a ticket order exceeds a set Order Total.
Add More Actions
To do more with the same submission, click + below the action to add another step.
For example, you can also add the guest to your email marketing list or create a contact in your CRM. The number of steps you can add depends on your Zapier plan.
Filtering Submissions
To run actions only for certain submissions, add a Filter by Zapier step between the trigger and the action.
For example, add a filter that continues only when Guest RSVP Status is confirmed, so declined guests are not added to your spreadsheet
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 form answers. Additional fields may be added over time.
Submission and Form
Submission ID – unique ID of the submission
New or Edited –
neworupdatedSubmitted At, Last Edited At – date and time in UTC
Confirmation Page URL – link to the guest's confirmation page
Price – amount for this guest's registration or ticket
Event Name
Form ID, Form Name, Form Type
Order Details
Order ID – unique ID of the order
Order Buyer Name, Order Buyer Email – the person who submitted the form or purchased tickets
Order Total, Order Currency
Order Receipt URL – link to the order receipt
Guest Details
Guest fields are prefixed with Guest, for example Guest Full Name, Guest Email, Guest Company and Guest RSVP Status. See Guest Triggers for the full list.
Plus-Ones
Included when the form allows plus-ones:
Number of Plus-Ones
Plus Ones – details of each plus-one
Custom Questions
Included when the form has custom questions:
Answers – each question as its own field, labeled with the question text
Answers Summary – all questions and answers in a single text field, useful for notes, emails and chat messages