TABLE OF CONTENTS
Triggers
New Event Ticket
New Event Ticket triggers when a new ticket is created for a selected Event in TicketSignup.
Users who authenticated the app as a Partner (not an Event Director) must define the desired Event in the trigger parameters when configuring the component.
Users may optionally include questions, raffle tickets, and ticket check-in counts in the trigger payload.
In order to support bulk data entry events, the user must enter a unique storage_key in the trigger setup.
New Event Ticket is a Zapier trigger and will always be followed by at least one action. The output of the New Event Ticket trigger returns a payload of data that may be used for mapping in subsequent actions.
Setup
Field |
How it works/What it does |
Event |
|
Include Questions? |
|
Include Raffle Tickets? |
|
Include Ticket Checkin Counts? |
|
Define your TicketSignup storage key. |
|
Features and Functionality
Features:
-
The payload of data returned by this trigger includes the Event Name, Ticket Group, Ticket Group Level, and Ticket Status as human readable data elements.
-
Date/time fields have been converted to ISO-8601 format in the UTC timezone. Users will want to use Formatter by Zapier to convert the date to their desired timezone and/or date format.
-
Amount fields have been formatted as a number (10,7.5), not currency ($10.00; $7.50) to align with Zapier best practice.
-
If custom questions are included in the trigger setup, the return will parse and format each separate custom question and response as {question id} :: {response}.
Behavior:
-
This trigger only runs based on the creation of a new ticket via the Event website or offline data entry methods (manual import or CSV import). It does not trigger based on modifications to existing tickets.
-
TicketSignup allows users to clear (cancel) a ticket within 15 minutes of submitting the purchase. The New Event Ticket trigger will run based on the creation of the ticket, not following the 15 minute pending window.
-
This component employs TicketSignup’s GET /storage endpoint to store the ID of the last ticket processed via the Zap. Below is the order of operations for this solution:
-
User defines a unique storage_key in the trigger parameters.
-
Zap is turned on by the user.
-
GET /tickets with DESC sort by ticket_id to get the most recent ticket ID
-
POST /storage to set the ticket_id as the cursor
-
If there are no tickets for the selected Event, the Zapier app will default with value to “1”.
-
-
-
Zapier polls the endpoint based on user’s polling interval (determined by Zapier subscription level)
-
GET /storage using the Zap’s storage_key to retrieve the ID of the last processed ticket
-
GET /events for the selected Event
-
GET /tickets with after_ticket_id parameter using the ticket_id returned from /storage; sort is ASC to sort tickets after the defined ticket_id from oldest to newest
-
POST /storage to set the new cursor value
-
If no new tickets in polling interval, previous cursor is set again (no change)
-
If tickets were returned in polling interval, the most recent ticket processed is set as the cursor value
-
-
-
Limitations:
-
This trigger will not run for modifications to existing ticket purchases.