Step types
notify has eleven step types. The list is the registry in internal/steptype; it is also what POST /v1/workflows accepts in type.
| Type | Kind | What it does |
|---|---|---|
in_app | Channel | Puts a message in the subscriber’s inbox. |
email | Channel | Sends an email through an email integration. |
push | Channel | Sends a push notification (ntfy, Expo, FCM, Web Push, or a push webhook). |
chat | Channel | Posts to Discord, Telegram, Slack, WhatsApp, Mastodon, Bluesky, or a chat webhook. |
sms | Channel | Sends an SMS through Twilio, SignalWire or Amazon SNS. |
delay | Flow | Waits: a fixed time, until a scheduled time of day, or until a time in the payload. |
digest | Flow | Collects events for a window and sends one run with the batch. |
throttle | Flow | Fails the run when a subscriber exceeds a rate. |
http_request | Action | Calls an HTTP endpoint and exposes the response to later steps. |
stream | Channel | Publishes an event to the environment’s durable feed. |
agent_message | Action | Posts a message to an agent’s conversation and starts its turn. |
All steps run in the order listed in the workflow. Channel steps accept filters, a condition.
Gates
Channel steps (in_app, email, push, chat, sms, stream) apply their gates in this order:
- The step’s condition. False, or not evaluable, records a message with status
skippedandskipReasonconditionorcondition_invalid. - The step’s inline
throttle({"limit": n, "windowSec": s}incontrolValues), if set. Over the limit records a message with statusthrottled. The budget is per environment, subscriber and workflow. - The subscriber’s preferences. A disabled channel records
skippedwithskipReasonpreference, unless the workflow iscritical. If the preference lookup itself fails, the send proceeds. - The recipient’s address. A step whose recipient has none for the channel records
skippedwithskipReasonno_email(email),no_device(push: no topic, device token or web push subscription) orno_channel(chat, on a provider that addresses each recipient: telegram, slack, whatsapp). No provider is called, and the run carries on. Anin_appstep needs no address, andsmshas its ownno_verified_phone. - The send. A transient provider error (a timeout or a 5xx) makes the engine retry the task. A permanent error records a message with status
errorand the error text. A scope with no integration for the channel recordserrorwitherrorClassnot_configured; it is a setup fault, so it never counts against an integration’s health.
Fields in controlValues that hold text are Handlebars templates.