POST
/
workflows
curl -X POST \
  -H 'Authorization: Bearer $API_KEY' \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json' \
  -d '{"name": "My Scripted Workflow", "team_id": "YOUR_TEAM_ID", "is_external": false, "canvas_type": 0, "public": false}' \
  '$BASE_URL/workflows'
{
  "id": "d0763222-8f38-46aa-a96e-2532038e49b8",
  "name": "My Scripted Workflow"
}

Headers

​
x-api-key
string
required

Your API key. This is required by most endpoints to access the API programmatically. You can view your x-api-key using the 'Profile' tab on the website.

​
Authorization
string
required

Bearer token for authentication (JWT).

Body

application/json

JSON data defining the workflow to be created.

The body is of type object.

Response

200
application/json

Successfully created workflow (some code returns 200). Returns the new workflow in JSON.

The response is of type object.

POST
/
workflows
curl -X POST \
  -H 'Authorization: Bearer $API_KEY' \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json' \
  -d '{"name": "My Scripted Workflow", "team_id": "YOUR_TEAM_ID", "is_external": false, "canvas_type": 0, "public": false}' \
  '$BASE_URL/workflows'
{
  "id": "d0763222-8f38-46aa-a96e-2532038e49b8",
  "name": "My Scripted Workflow"
}

Headers

​
x-api-key
string
required

Your API key. This is required by most endpoints to access the API programmatically. You can view your x-api-key using the 'Profile' tab on the website.

​
Authorization
string
required

Bearer token for authentication (JWT).

Body

application/json

JSON data defining the workflow to be created.

The body is of type object.

Response

200
application/json

Successfully created workflow (some code returns 200). Returns the new workflow in JSON.

The response is of type object.