> ## Documentation Index
> Fetch the complete documentation index at: https://docs.notifique.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> When something happens in your system or on a channel, Notifique runs a sequence of steps.

<Tip>
  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.
</Tip>

## 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

| Concept            | What it is                                                   |
| ------------------ | ------------------------------------------------------------ |
| **Automation**     | Full flow (step graph), enabled or paused                    |
| **Event**          | Registered name for a system fact (`order.paid`)             |
| **Run**            | One execution of the flow for a recipient                    |
| **Trigger**        | How the flow **starts** (event, webhook, or inbound message) |
| **AI assistant**   | Conversation “brain”, instructions + model + knowledge + MCP |
| **Knowledge base** | Indexed docs the AI queries (RAG)                            |
| **MCP**            | External tools for the AI (Gmail, calendar, your API)        |

**Campaign** (Contacts tab) = one-shot bulk send. **Automation** = **repeatable** sequence whenever the trigger fires again.

<Note>
  **Automation webhook** (starts the flow) ≠ **Notifique webhook** (channel delivery status, etc.). See [Webhooks](/en/guides/webhooks/index) in Guides.
</Note>

## Three ways to trigger

| Way                                                    | Who starts                    | Example                             |
| ------------------------------------------------------ | ----------------------------- | ----------------------------------- |
| **[Event](/en/automations-api/como-funciona/eventos)** | Your backend via API          | `POST` Send event with `order.paid` |
| **HTTP webhook**                                       | External system (POST to URL) | Zapier, ClickUp, ERP                |
| **Inbound message**                                    | Customer on channel           | Chatbot with AI assistant           |

## Common step types

| Type               | What it does                              |
| ------------------ | ----------------------------------------- |
| **Trigger**        | Starting point (one per flow)             |
| **Send template**  | Message via email, SMS, WhatsApp…         |
| **Delay**          | Time pause                                |
| **Condition**      | `true` / `false` branches (both required) |
| **AI assistant**   | Reply using knowledge base and/or MCP     |
| **Update contact** | Tag, field, or topic                      |
| **End**            | Stops the branch                          |

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.

<Info>
  Each API Key belongs to **one** workspace. In v1 **do not send** `x-workspace-id`. Use **`Idempotency-Key`** when sending events.
</Info>

## 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](/en/automations-api/como-funciona/assistentes), [Knowledge base](/en/automations-api/como-funciona/base-de-conhecimento), and [MCP integrations](/en/automations-api/como-funciona/integracoes-mcp).

## When to use?

Great for **post-event sequences**, **chatbots**, and **follow-ups** (wait + second message). For a **one-off** send without repeating, use [templates](/en/template-api/como-funciona/quick-start) or the channel API.

## Next steps

* [Quick Start](/en/automations-api/como-funciona/quick-start): first event and flow
* [Events](/en/automations-api/como-funciona/eventos): register and trigger
* [Webhook events](/en/automations-api/como-funciona/eventos-do-webhooks): runs and status via webhook
* [Assistants](/en/automations-api/como-funciona/assistentes): configure AI
* [Knowledge base](/en/automations-api/como-funciona/base-de-conhecimento) · [MCP integrations](/en/automations-api/como-funciona/integracoes-mcp)
* [Use cases](/en/automations-api/como-funciona/casos-de-uso)
* [API Key scopes](/en/automations-api/como-funciona/escopos-da-api-key)