Review an automation before it goes live
What going live checks, on what’s on screen (its draft) (D195): the trigger and who can enter, the steps, each live email (made, a subject in every locale it’s written in, compiling) and each sender (its domain verified with DMARC, its account connected), each problem with the step it’s on. Errors stop it going live; warnings are worth knowing (a draft email is skipped, a path without conditions is never taken).
What going live checks, on what’s on screen (its draft) (D195): the trigger and who can enter, the steps, each live email (made, a subject in every locale it’s written in, compiling) and each sender (its domain verified with DMARC, its account connected), each problem with the step it’s on. Errors stop it going live; warnings are worth knowing (a draft email is skipped, a path without conditions is never taken).
apiKey readAuthorizationBearer <token>A workspace API key (pf_…), created under Developers → API keys.
Scope: read
id*string^(auto)_[0-9A-Za-z]{8}$OK
application/json- response
ready*booleanchecks*array<>curl -X GET 'https://api.postforge.dev/v1/automations/string/review'{ "ready": true, "checks": [ { "check": "trigger", "ok": true, "issues": [ { "path": "string", "message": "string", "stepId": "string", "severity": "error" } ] } ]}Make an email step’s email from a template POST
Copies the template’s latest document (or a starter’s, in the workspace’s default locale) into a new email of the step’s own (D174), with no subject yet, and saves the automation’s draft with it. 404 when the draft has no such step; 422 `not_an_email_step`; 409 `email_exists` when the step has one already.
What saving an automation’s changes does to the people in it GET
For the people in it now, per step they’re on: whether moving them to the changed automation lets them continue, changes their wait (counted from when they reached it), moves them on at once (that wait is over), or makes them leave (their step is gone).