Workflow Triggers

A trigger is what starts a workflow. Sift workflows are driven by three kinds of trigger: matching a condition (an inline filter you build right in the workflow), a saved-search match (an action matches a filter you've saved separately), or a schedule (a recurring cron run). A single workflow can have more than one trigger attached, and each one independently kicks off the same workflow.

Set them up on the Automations tab of Settings → Workflows.

At a glance

The three trigger types

• Match a condition: build a filter inline, without a separate saved search - keyword, text pattern, sentiment, tag, score, likes, and more, grouped by content, classification, date and volume, groups and users, and source. Use this when the condition is specific to this one workflow and you don't need to reuse it elsewhere.
• Saved-search match: the workflow runs when an action matches the criteria of a saved search you've already built. Use this when the same condition powers a queue, a notification, or more than one workflow, so you only maintain it in one place.
• Scheduled (cron): the workflow runs on a recurring schedule defined by a cron expression and timezone. Use it for digest reports, periodic SLA checks, or queue sweeps that aren't tied to a single action.

Multiple triggers

A workflow can have several triggers attached at once - for example, a condition match and a daily schedule together. Each trigger is evaluated independently and runs the same downstream steps.

Full action context

When a condition or saved-search trigger fires, the workflow receives the full action: its id, source platform, channel, tags, status, queue, assignee, and the rest of its fields. Downstream steps can reference any of them without an extra lookup.

Choosing a trigger

• For a condition you'll only use in this one workflow, build it inline with Match a condition.
• For a condition you already use elsewhere (a queue, a notification, another workflow), reuse it as a saved-search match instead of rebuilding it.
• For periodic work that isn't tied to a specific action, use a scheduled trigger.

Related