What saving an automation’s changes does to the people in it
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).
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).
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
active*integersteps*array<>curl -X GET 'https://api.postforge.dev/v1/automations/string/save-impact'{ "active": 0, "steps": [ { "stepId": "string", "people": 0, "outcome": "continues" } ]}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.
Save an automation’s changes POST
Puts its unsaved changes in use, as a new version in its history. `people: move` (the default) moves everyone in it to the changed automation, as `saveImpact` says; `keep` lets them finish the version they’re on. 422 `checks_failed` with each problem in its place; 409 `nothing_to_save` when there are no unsaved changes.