Using Triggers

Decide how and when your scenarios start—on a schedule, webhook, or from another flow.

Triggers control when a scenario begins execution. Pick the trigger that matches your business event, then keep inputs predictable so downstream steps are easy to maintain.

Trigger types

• Manual/Test: Run ad hoc to validate changes or replay a payload.
• Schedule (CRON): Fire on a cadence (hourly, daily, weekly) for feeds, reconciliations, or audits.
• Webhook/API: Start on inbound HTTP calls when marketplaces, ERPs, or custom apps send events.
• Email: Kick off processing when messages arrive at a designated address or inbox.

Setup checklist

1. Decide the expected payload shape and document it in the scenario’s input schema.
2. Add authentication or secret validation for webhook/API triggers.
3. Set retry logic or idempotency keys if the source may send duplicates.
4. Test with representative payloads before promoting the trigger to production.

Operating tips

• Keep triggers narrow—one trigger per scenario is easier to reason about than multiplexed handlers.
• Use schedules for bulk or catch-up work, webhooks for real-time updates, and email when partners cannot send webhooks.
• Log enough context (order IDs, channel references) at the entry step to speed up troubleshooting.