REreacherapp
Workflows

Publish a workflow

Changed on

Validate, snapshot the definition, compile one engine automation per outbound step, and start running. This is the call that makes a workflow send: the compiled rows go to the live outreach engine and begin messaging and inviting real creators within minutes, inside the shop's daily limits. Refused when validation has blocking issues. Republishing updates rows in place; creators already mid-flight finish on the version they entered under, and reroute says where creators standing on a removed step should go.

post/workflows/{workflow_id}/publish

Request

  • Base URL
    https://api.reacherapp.com/public/v1
  • URL
    https://api.reacherapp.com/public/v1/workflows/{workflow_id}/publish
  • Auth
    API key in header x-api-key and API key in header x-shop-id

Path parameters

workflow_idstring required

The workflow's uuid, as POST /workflows/list returns it.

Headers

Idempotency-Keystring nullable

Request body

rerouteobject

For steps removed since the last publish: where their parked creators go. Keyed by the removed step id; the value is a surviving step id, or "exit" to end the workflow for them.

Response

Successful Response

Changes