A trigger is the moment an automation starts: a purchase, a cart left behind, a scan at the door. Actions are what Trybe does next: email, text, promo code, list changes. Waits, conditions and branches tie them together.
Ten triggers, including any interaction recorded in your data
Seven actions: email, text, promo code, campaign, lists, property, note
Wait for a duration, a date or a set time before the event
Only continue if… and if/otherwise branches, nested in Advanced
Re-entry rules: once ever, once per event, every X days or every time
Triggers and actions are the building blocks of every Trybe automation, for organizers and promoters. A trigger is what starts the run: New follower, New purchase, Abandoned cart, Refund request, Before an event, After an event, Event goes live, Added to a list, Birthday, or Something in your data, any recorded interaction such as a door scan. Filters narrow a trigger, for example to one event. Actions are what Trybe does next: send an email, send a text, create a promo code unique to the person, schedule a campaign to a whole segment, add to or remove from a list, set a contact property, or add a note for your team. Messages can go to the fan, you or a teammate. Between actions, Wait holds for a duration, until a date or until a set time before the event, at the hour you choose; Only continue if… checks a condition; If / Otherwise splits the path. Re-entry rules decide if a person goes through once ever, once per event, at most every X days or every time.
Pick what starts the run and add filters so only the right cases enter: one event, one list, one kind of interaction.
Add up to three actions in Guided mode, more in Advanced: email, text, promo code, campaign, list, property, note.
Insert waits with a stop rule, Only continue if… checks, and If / Otherwise branches. Set how often the same person can re-enter.
Review the cost per run and switch on. Each run's trace shows the trigger, every action, every wait and every condition it met.
Ten: New follower, New purchase, Abandoned cart, Refund request, Before an event, After an event, Event goes live, Added to a list, Birthday and Something in your data. The last one turns any interaction Trybe records, such as a door scan, into a trigger.
A filter sits on the trigger and decides who enters at all, for example only purchases for one event. A condition sits between steps: Only continue if… stops the run when it fails, and If / Otherwise sends people down two different paths.
A Wait step holds the run for a duration, until a date, or until a set time before the event, and can land at a chosen hour so a message arrives at 10 AM rather than 3 AM. Every wait needs a stop rule, such as “they bought a ticket”, so the run is cancelled if the situation changes.
Yes. Any email or text can go to the fan, to you or to a team member, and internal sends are free. The Add a note action leaves context on the contact for whoever handles it next.
Yes, with the Schedule a campaign action, the only step that targets a whole segment rather than the person who triggered the run. It is useful after Event goes live, for example, to announce the event to a saved segment.
Guided shows the automation as one plain sentence, “When someone buys a ticket, Trybe will send…”, with up to three actions and one split at the end. Advanced opens the full canvas with nested if/otherwise branches, reordering and more steps.
Flows that run on their own when fans follow, buy, abandon a cart or have an event coming up
A daily cap per person, honoured unsubscribes, stop rules on every wait and quiet hours, enforced by Trybe
Live audiences built from rules: people join and leave on their own as they buy, open, attend or move
Free for organizers hosting on Trybe. No credit card, two-minute setup, works in English and French.