Activate an automation
Turn a draft automation on.
https://app.usenotix.dev/api/v1/automations/{id}/activateNeeds a full access key. Sending access keys cannot call this. Key permissions lists the extra rules some calls have.
Turn a draft automation on. Notix runs every check the dashboard runs: at least one email step, each sending from a verified domain that is not paused for its reputation, with an unsubscribe link and nothing the deliverability check blocks. A refusal is 400 with the reason. A team Notix has not reviewed yet comes back with status PENDING_REVIEW: it sends nothing until Notix approves it.
Only a draft is activated; a paused automation answers 409 and is resumed with POST /v1/automations/{id}/resume. A key with an approval policy that only saves drafts (or a threshold of 0) cannot activate: there is no approval step, so it answers 403 with reason APPROVAL_POLICY. Once on, every email counts against the team's daily and monthly limits, and every enrolment through the API against the key's own caps. A team can activate 10 automations a minute. Check first with GET /v1/automations/{id}/preflight.
Who can call it
A full access key created by a team admin, as on the dashboard. Every refusal is 403:
| Code | Why |
|---|---|
SCOPE_DENIED | The key is not a full access key (send-only, read-only or live AI). |
FORBIDDEN | The key was made by a team member without admin rights, or before Notix recorded who made each key. Create a new key as a team admin. |
DOMAIN_PINNED | The key is limited to one domain and an email step, or the sender, is on another. |
A key limited to one domain sees only automations whose every email step sends from its domain; any other automation answers 404.
Path parameters
Headers
Bearer followed by your API key.
Errors
A check refused it: no email step, an unverified or paused domain, a missing unsubscribe link, or the deliverability check.
`SCOPE_DENIED`: the key is not a full access key (send-only, read-only or live AI). `FORBIDDEN`: the key was made by a team member without admin rights, or before Notix recorded who made each key. `DOMAIN_PINNED`: the key is limited to one domain and an email would send from another. `FORBIDDEN` with `details.reason` APPROVAL_POLICY: the key's approval policy does not let it turn a journey on.
No journey with this id for the calling team (or, for a pinned key, on its domain).
The journey is not a draft. A paused journey is resumed with POST /v1/journeys/{id}/resume.
The team activated 10 journeys in the last minute.
Every error has the same shape. See all error codes.
curl -X POST "https://app.usenotix.dev/api/v1/automations/<id>/activate" \
-H "Authorization: Bearer $NOTIX_API_KEY"
import { Notix } from "notix-js";
const notix = new Notix(process.env.NOTIX_API_KEY);
const { data, error } = await notix.automations.activate("jrn_123");
console.log(data?.status); // ACTIVE, or PENDING_REVIEW while Notix reviews the team
{
"id": "cly1jrn8x0000abcd1234",
"name": "Welcome series",
"status": "ACTIVE",
"triggerType": "CONTACT_ADDED",
"contactBookId": "cly1book0000abcd1234",
"segmentId": "cly1seg00000abcd1234",
"exitWhenLeavesSegment": false,
"triggerEvent": "payment.failed",
"steps": [
{
"id": "cm1x8f3k20001qz7v5b9d2e4a",
"type": "EMAIL",
"from": "Acme <receipts@acme.com>",
"subject": "Your receipt for order 4471"
}
],
"connections": [
{
"from": "trigger",
"to": "stp_a1b2c3d4e5f6"
}
],
"copiedFromId": "cm1x8f3k20001qz7v5b9d2e4a",
"stats": {
"enrolled": 1,
"active": 1,
"completed": 1,
"exited": 1,
"failed": 1,
"sentByStep": {
"stp_abc123": 12
}
},
"createdAt": "2026-10-01T09:00:00Z",
"updatedAt": "2026-10-01T09:00:00Z"
}