Dry-run an automation
Runs its draft (what’s on screen) against real people and their real data without doing anything (D207): for the times its trigger fired in the last days (up to 200) or for people picked, whether each would enter and why not, and the path they’d take step by step (what each step would do and why) on a pretend clock, waiting where a wait ends after now. Nothing is written, sent or handed out.
Runs its draft (what’s on screen) against real people and their real data without doing anything (D207): for the times its trigger fired in the last days (up to 200) or for people picked, whether each would enter and why not, and the path they’d take step by step (what each step would do and why) on a pretend clock, waiting where a wait ends after now. Nothing is written, sent or handed out.
apiKey readAuthorizationBearer <token>A workspace API key (pf_…), created under Developers → API keys.
Scope: read
id*string^(auto)_[0-9A-Za-z]{8}$application/json- body
who*|OK
application/json- response
people*array<>truncated*booleancurl -X POST 'https://api.postforge.dev/v1/automations/string/dry-run' \ -H 'Content-Type: application/json' \ -d '{ "who": { "type": "recent" }}'{ "people": [ { "profile": { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "name": "string", "email": "string" }, "triggeredAt": "2019-08-24T14:15:22Z", "fired": true, "outcome": "entered", "end": "completed", "until": "2019-08-24T14:15:22Z", "path": [ { "stepId": "string", "outcome": "waited", "detail": { "property1": null, "property2": null }, "at": "2019-08-24T14:15:22Z" } ] } ], "truncated": true}Review an automation before it goes live GET
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 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).