Skip to main content
An automation is a playbook: when X happens, run steps (send, wait, AI, condition…). An event is the fact name. A run is each time the playbook runs for one person.

​
What are Automations in Notifique?

The journey engine: you build a step graph in the dashboard or via API. When the trigger fires, a run walks through template sends, delays, AI assistants, contact updates, and more. You can:
  • Trigger from your API (order.paid, user.created)
  • Receive HTTP webhooks from external tools (Zapier, ERP)
  • React to inbound messages (WhatsApp, SMS, widget…)
  • Inspect runs and audit what happened
Think of a theater script: the trigger raises the curtain; each step is a scene.

​
Concept map

Campaign (Contacts tab) = one-shot bulk send. Automation = repeatable sequence whenever the trigger fires again.
Automation webhook (starts the flow) ≠ Notifique webhook (channel delivery status, etc.). See Webhooks in Guides.

​
Three ways to trigger

​
Common step types

Automation status: ENABLED (fires) or PAUSED (does not fire). Stop an active run via API with automations:write.

​
What’s in the v1 API

Routes with the /v1/ prefix and API Key auth (sk_live_... / sk_test_...):
  • Events, register and trigger (events:read, events:write)
  • Automations, graphs, stop flow, list runs (automations:read, automations:write)
Full reference in the Automations and events spec in the sidebar.
Each API Key belongs to one workspace. In v1 do not send x-workspace-id. Use Idempotency-Key when sending events.

​
Dashboard (outside v1 API)

Knowledge bases, assistants, and MCP integrations are configured in the dashboard (Automations → Bases, Assistants, MCP). There are no public /v1/ routes for these in this documentation, use Assistants, Knowledge base, and MCP integrations.

​
When to use?

Great for post-event sequences, chatbots, and follow-ups (wait + second message). For a one-off send without repeating, use templates or the channel API.

​
Next steps