Skip to main content
PUT
Declares work to run on a schedule: an ordered list of named steps, each an

Authorizations

Authorization
string
header
required

An Erdo API key (erdo_api_...) or scoped token (erdo_token_...).

Body

application/json
destination
Where to record what a run produced. Omitting a destination is normal for a · object

declaration whose steps act rather than report.

enabled
boolean
name
string

run several without either replacing the other. Lowercase letters, digits, hyphens and underscores.

schedule
string

at eight.

steps
One step of a scheduled declaration. A step is EITHER an action to invoke · object[]

under its name for the steps that follow.

timezone
string

"America/New_York". Defaults to UTC. It matters for anything comparing against a provider's own day boundary: an ad account reports yesterday in the account's timezone, and a run at 08:00 UTC is the previous afternoon in Miami.

workstream
string

bound what this run may act on. The refs are read at run time and handed to the steps as {{scope.ids}} and {{scope.refs}}; nothing is copied here, so publishing a new set takes effect on the next run with no edit to this declaration.

A workstream governing nothing yet means a run that does nothing and says so — never a run with no filter. Omit this only for a declaration that genuinely acts on no provider objects.

Response

Success response

destination
Where to record what a run produced. Omitting a destination is normal for a · object

declaration whose steps act rather than report.

enabled
boolean
job_id
string

history can be inspected through the automation surfaces.

name
string
schedule
string
steps
One step of a scheduled declaration. A step is EITHER an action to invoke · object[]
timezone
string
workstream
string