Email Triggers
An email trigger fires a duty within about a minute of a matching email landing in a connected inbox, so a specialist can react to order alerts, support tickets, or new leads almost as soon as they arrive.
How an email trigger works
Connect an inbox in the Launchpad, then attach an email trigger to a duty. Every new message is checked against the trigger's rules; a match starts the duty's run right away — you don't wait for the next scheduled time.
- Open the duty's editor and add an email trigger.
- Set the matching rules (below).
- Save. New mail is checked continuously; a match runs the duty within about a minute.
Matching rules
Narrow the trigger so it only fires on mail that actually matters:
- From / domain — match a specific sender address or an entire domain, such as everything from your storefront's order notifications.
- Subject include — only fire when the subject contains a word or phrase, like "New order" or "Ticket #".
- Subject exclude — skip mail even if it otherwise matches, useful for filtering out receipts, digests, or auto-replies that share a sender with real alerts.
Extra folders
By default a trigger watches the inbox. You can add extra folders to watch too — Spam is the common one, since some automated order or ticket systems land there by mistake and you don't want to miss them.
Best uses
Email triggers work best for anything that already arrives by email and needs a fast reaction:
- Order alerts from a storefront or payment processor.
- New support tickets from a helpdesk that emails on creation.
- Lead notifications from a contact form or ad platform.
Keep a light schedule as backstop
Email delivery is generally reliable but not instant by guarantee, and a mail provider hiccup can delay a trigger. Give the same duty a light recurring schedule too — every hour, say — so it also catches anything the trigger missed. Runs from the schedule and the trigger use the same instructions and autonomy setting.
Rate caps
A burst of matching mail — a marketing blast forwarded to a hundred people, for instance — is capped so it can't fire a duty over and over in a short window. When a rate cap is hit, you get a notification instead of the run silently being dropped, so you always know a trigger was suppressed and can catch up manually.