Flows
A flow is a plan of one or more steps that Attlaz executes. Each run of a flow is a flow run. A flow is made up of:
- A trigger — what starts the flow (an API call, a webhook, a schedule, or an incoming email).
- Logic — conditional steps (for example, an
ifthat branches on the data). - Actions — the work the flow performs. An action can be defined in a ready-made template or in your own code.
- Reports — steps that output or notify, such as sending an email, SMS, or a Slack/Teams message.
Types
| Type | Description |
|---|---|
| Scheduled | Runs automatically on a time-based schedule. |
| Direct | Runs on demand — when its API, webhook, or email trigger fires. |
Triggers
A trigger places a flow run request on the queue. Some parameters of the run can be overridden when the trigger fires.
| Type | When it fires | Configuration |
|---|---|---|
| API | When the flow's API endpoint is called | — |
| Webhook | When the flow's webhook URL is called | Webhook key |
| Schedule | According to a schedule | Schedule definition |
| When an email arrives in a monitored mailbox | Mailbox to monitor, email filters |
Statuses
A flow run moves through the following statuses. A run stays Pending until a runner actually begins executing it — it does not flip to Running the moment a runner picks it up.
| Status | Meaning |
|---|---|
| Pending | The run is waiting to be handled by a runner. |
| Running | The run is being executed by a runner. |
| Complete | The run finished successfully. |
| Failed | The run could not complete. |
| Stopped | The run was stopped while executing. |
| Canceled | The run was stopped before a runner picked it up. |