Skip to main content
POST
Add a step to a flow (trigger as step 1, actions as step 2+)

Authorizations

Authorization
string
header
required

Use a Bearer token to access these API endpoints. Example: "Bearer {your-token}"

Path Parameters

uuid
string<uuid>
required

Body

application/json
kind
enum<string>
required
Available options:
trigger,
action
app_uid
string
required

From GET /flow/apps.

trigger_key
string | null

Required when kind=trigger. From GET /flow/apps/{uid}/triggers.

action_key
string | null

Required when kind=action. From GET /flow/apps/{uid}/actions.

app_connection_uuid
string<uuid> | null

Required for connect-category apps; must be null for builtin apps.

agent_uuid
string<uuid> | null

Required for Agents-app actions.

config
object | null

Action/trigger-specific config. Use {{stepN.field}} to template values from upstream steps.

insert_after_step_uuid
string<uuid> | null

Insert mid-chain after this step. Subsequent steps shift up by 1; their {{stepN.field}} references are rewritten.

parent_step_uuid
string<uuid> | null

Use to nest this step as a branch child of an if_condition. Requires branch_key.

branch_key
enum<string> | null
Available options:
true,
false

Response

Created

data
object

One step of a flow. The first step in a flow is always a trigger (kind=trigger); subsequent steps are actions. Branch children (under an if_condition) appear flat in the parent flow's steps[] with parent_step_uuid + branch_key populated.