Skip to main content
POST
Create a new workflow

Authorizations

Authorization
string
header
required

A session token from subscriber login, used by subscriber.dev's own apps. Requests about an environment also need its ID in the x-environment-id header. From your own code, use an API key.

Body

application/json
key
string
required

Stable identifier used to trigger this workflow, e.g. "user-signup". Unique within the environment.

Required string length: 1 - 255
name
string
required
Required string length: 1 - 255
steps
object[]
required
Required array length: 1 - 50 elements
description
string
Maximum string length: 2000
type
enum<string>
default:automation

Purely organizational: automation workflows are meant to be triggered individually per-subscriber; broadcast workflows are meant to be fanned out via the broadcast endpoint. Either can technically still be used either way.

Available options:
automation,
broadcast
channels
object

Settings for each channel this workflow sends on. Channel-specific, so the workflow itself stays channel-neutral.

triggers
object[]

Events from connected integrations that start this workflow for the person they're about. Automation workflows only; the integration must be connected first.

Maximum array length: 50
exitConditions
object[]

Events from connected integrations that stop this workflow for the person they're about: their active runs are cancelled and unsent steps never send. Checked before triggers, so an event in both restarts the workflow. Automation workflows only; the integration must be connected first.

Maximum array length: 50

Response

publicId
string
required
key
string
required
name
string
required
description
string | null
required
status
enum<string>
required
Available options:
active,
paused
type
enum<string>
required
Available options:
automation,
broadcast
channels
object
required

Settings for each channel this workflow sends on.

steps
object[]
required
triggers
object[]
required
exitConditions
object[]
required
createdAt
string<date-time>
required
Pattern: ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d:[0-5]\d(?:\.\d+)?(?:Z))$
updatedAt
string<date-time>
required
Pattern: ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d:[0-5]\d(?:\.\d+)?(?:Z))$
editUrl
string

Link to edit this workflow's emails in the web editor. Share it when someone wants to tweak the copy or preview an email.