Shopify Flow triggers

Easy Tickets sends five triggers to Shopify Flow. A workflow can start when a ticket sells, a guest checks in, a ticket changes date, an event sells out or someone joins a waitlist. There is nothing to set up in Easy Tickets.

Build a workflow

1. In Shopify Flow, click Create workflow.
2. Click Select a trigger and choose one of the Easy Tickets & Events triggers below.
3. Add conditions and actions with the + button.
4. Click Turn on workflow.

To put a trigger field into an action, use Add a variable under the action's field.

The triggers send text and number fields only. They carry no Shopify order or customer, so an action that changes an order or a customer needs a lookup first. The recipes below show how.

The five triggers

Ticket Purchased

Starts once for every ticket, so an order with 4 tickets starts 4 runs. It fires for Shopify orders from the online store and POS, for class-pack credit bookings and for seated sales. Free registrations do not start it.

• Customer email: the email on the ticket. When the popup collected a guest's own email, it is the guest's.
• Customer name
• Ticket type
• Ticket code
• Event name
• Quantity: how many tickets this order bought for this event.
• Event id and Ticket number: together they point to one ticket.
• Language: the ticket's language, empty when the store sells in one language.
• Order id: the Shopify order. For a class-pack booking, the order that bought the pack.
• Booking source: "shopify" for a bought ticket, "class-pack" for a redeemed credit.
• Class pass id: the redeemed class pass, empty for ordinary purchases.

Attendee Checked In

Starts on every new entry, from every door: the phone check-in page, Shopify POS and Manage check-in on the Shopify order page. A 3-entry pass can start it three times.

• Attendee name and Attendee email
• Ticket type and Ticket code
• Event name: for a date of a recurring event, that date's own name.
• Check in count: how many entries the ticket has after this check-in.
• Event id, Ticket number and Language

Refused scans and undo start nothing. A scan repeated because its first answer got lost does not start a second run.

Ticket Moved

Starts when a ticket moves to a different date. That covers moves in Easy Tickets, moves from the Shopify order page and a customer changing their own date.

• Customer email and Customer name
• Ticket code
• Event name: the series name.
• Previous date and New date, written with your shop's date and time settings.
• Order name: the order number the ticket was bought on.
• Event id: the date the ticket is on now.
• Ticket number and Language

Putting a waiting ticket back on its own date does not start it.

Event Sold Out

Starts when the last ticket of an event or date sells. Its fields are Event name and Total tickets sold.

It fires only when every ticket type has a stock number and an order sells the last one. A ticket type without a stock limit never sells out, and free registrations do not start it.

Waitlist Signup

Starts when someone joins a waitlist. Its fields are Customer name, Customer email, Event name and Language.

Good to know

• Use Event id together with Ticket number to tell tickets apart. A ticket code repeats across dates and events.
• Language stays empty until you turn on customer languages.
• Refunds, cancellations and group-seat claims have no Flow trigger. They do reach Klaviyo; see Zoom, Klaviyo and Mailchimp.

Recipes

The recipe steps use Flow's own screen names as they read in September 2026, so check them in your own Flow editor.

Email your team when an event sells out

1. Click Create workflow, then Select a trigger, and choose Event Sold Out.
2. Add the action Send internal email.
3. In Email address, type your team's address. Flow does not allow a variable in this field.
4. Write a Subject. In Message, use Add a variable to insert Event name and Total tickets sold.
5. Click Turn on workflow.

Tell the door team when a VIP arrives

1. Choose the trigger Attendee Checked In.
2. Add a Condition: Ticket type is the name of your VIP ticket type.
3. On the True branch, add Send internal email. Put Attendee name and Event name in the Message.
4. Click Turn on workflow.

Tag the order when a ticket changes date

The trigger sends the order number as text, so the workflow finds the order first.

1. Choose the trigger Ticket Moved.
2. Add the action Get order data. Set Maximum number of results to 1.
3. Under Query, choose Advanced. Type name:"" and put the Order name variable between the two quotes with Add a variable.
4. Add For each loop (iterate) over the result of Get order data.
5. In Repeat for each item, add Add order tags with a tag such as date-changed.
6. Click Turn on workflow.

Tag ticket buyers and put them in a segment

1. Choose the trigger Ticket Purchased.
2. Add the action Get customer data. Under Query, choose Advanced. Type email:"" and put the Customer email variable between the quotes.
3. Add For each loop (iterate). In Repeat for each item, add Add customer tags with a tag such as event-attendee.
4. Click Turn on workflow.
5. In Shopify admin, go to Customers > Segments and click Create segment. Use the query customer_tags CONTAINS 'event-attendee', click Run query, then Save segment.

To tag only one event's buyers, add a Condition on Event name before the lookup.

Customer email is the email on the ticket. A guest's email may belong to nobody in your Shopify customers, and then the lookup finds no one and nothing is tagged.

See also

• Check in with any phone
• the free registration feature page