Skip to main content

Understanding Workflow Triggers

V
Written by Victor Themps

Every workflow starts with a trigger: the event that kicks it off. This article covers every trigger available when you click the Start Workflow node.

Select a trigger sidebar listing all available triggers

Available triggers

Trigger

Starts the workflow when

Page Registration

A landing page form is submitted.

Ambassador Approved

An ambassador application is approved.

Ambassador Rejected

An ambassador application is rejected.

Contact Tagged

A contact is tagged with one of the tags you specify.

Order Completed

Only available for Weeztix & Paylogic clients

A customer places an order that includes certain ticket types.

Ticket Personalised

Only available for Weeztix & Paylogic clients

All tickets of a specific type within an order have been personalised.

Ticket Scanned

Only available for Weeztix & Paylogic clients

A ticket of a selected type is scanned at the entrance.

Choosing which contacts a trigger applies to

Most triggers (all except Ambassador Approved and Ambassador Rejected) show a Specify trigger choice once you configure them:

Contact Tagged trigger configuration showing the Specify trigger options
  • New only — only contacts who meet the condition from now on (for Contact Tagged, that means only contacts tagged after you set up the workflow)

  • New and existing — both new occurrences and contacts who already matched before the workflow existed

  • Existing only — only contacts who already matched before the workflow existed

Important: If you want a workflow to catch up on contacts that already match (for example, everyone who already has the VIP tag), choose New and existing or Existing only: the default is usually New only, which won't touch anyone who already matched.

See How to Create a Workflow for how triggers fit into the full setup, and Understanding Workflow Actions for what happens next.

Did this answer your question?