Create Workflow

Create a new workflow. Optionally provide steps to define the workflow’s step graph.

When steps is omitted, the workflow is created with default steps (TRIGGER → PARSE). When steps is provided, the step graph is validated and the draft version is populated with the given steps.

Note: The default steps may change in the future. If your integration depends on a specific step graph, provide steps explicitly.

Create a new workflow. Optionally provide `steps` to define the workflow's step graph. When `steps` is omitted, the workflow is created with default steps (`TRIGGER` → `PARSE`). When `steps` is provided, the step graph is validated and the draft version is populated with the given steps. **Note:** The default steps may change in the future. If your integration depends on a specific step graph, provide `steps` explicitly.

Authentication

AuthorizationBearer

Bearer authentication of the form Bearer <token>, where token is your auth token.

Request

This endpoint expects an object.

namestringRequired

The name of the workflow.

stepslist of objectsOptional

The steps that define the workflow's processing graph. Each step has a `type`, a unique `name`, and optional `next` entries that define routing to downstream steps. When omitted, the workflow is created with default steps (`TRIGGER` → `PARSE`). The default steps may change in the future. See the [Configuring Workflows via API guide](https://docs.extend.ai/2026-02-09/workflows/configuring-workflows) for step definitions, branching patterns, and examples.

Response

Workflow created successfully

objectenum

The type of object. Always "workflow".

Allowed values:

idstring

The ID of the workflow.

namestring

The name of the workflow.

createdAtstringformat: "date-time"

The time (in UTC) at which the object was created. Will follow the RFC 3339 format.

Example: "2024-03-21T16:45:00Z"

updatedAtstringformat: "date-time"

The time (in UTC) at which the object was last updated. Will follow the RFC 3339 format.

Example: "2024-03-21T16:45:00Z"

draftVersionobject

A workflow version with its step definitions.

Errors

400

Bad Request Error

401

Unauthorized Error

402

Payment Required Error

403

Forbidden Error

404

Not Found Error

422

Unprocessable Entity Error

429

Too Many Requests Error

500

Internal Server Error

Create a new workflow. Optionally provide steps to define the workflow’s step graph.

Note: The default steps may change in the future. If your integration depends on a specific step graph, provide steps explicitly.

Bearer authentication of the form Bearer <token>, where token is your auth token.

API version to use for the request. If you’re using an SDK, you can ignore this parameter. If you are not using an SDK and do not specify a version, you will either receive a 400 Bad Request or be set to a previous legacy version. See API Versioning for more details.

API version to use for the request. If you're using an SDK, you can ignore this parameter. If you are not using an SDK and do not specify a version, you will either receive a `400 Bad Request` or be set to a previous legacy version. See [API Versioning](https://docs.extend.ai/2026-02-09/api-reference/api-versioning) for more details.

This endpoint expects an object.

The name of the workflow.

The steps that define the workflow’s processing graph. Each step has a type, a unique name, and optional next entries that define routing to downstream steps.

When omitted, the workflow is created with default steps (TRIGGER → PARSE). The default steps may change in the future.

See the Configuring Workflows via API guide for step definitions, branching patterns, and examples.

Workflow created successfully

The type of object. Always "workflow".

The ID of the workflow.

The name of the workflow.

The time (in UTC) at which the object was created. Will follow the RFC 3339 format.

Example: "2024-03-21T16:45:00Z"

The time (in UTC) at which the object was last updated. Will follow the RFC 3339 format.

Example: "2024-03-21T16:45:00Z"

A workflow version with its step definitions.

The steps that define the workflow’s processing graph. Each step has a type, a unique name, and optional next entries that define routing to downstream steps.

When omitted, the workflow is created with default steps (TRIGGER → PARSE). The default steps may change in the future.

See the Configuring Workflows via API guide for step definitions, branching patterns, and examples.

1	from extend_ai import Extend, WorkflowStepDefinition_Trigger, SimpleNextEntry, WorkflowStepDefinition_Parse, WorkflowStepDefinition_Extract, ExtractStepDefinitionConfig, ExtractorRef, WorkflowStepDefinition_HumanReview
2
3	client = Extend(
4	token="YOUR_TOKEN_HERE",
5	extend_api_version="2026-02-09",
6	)
7
8	client.workflows.create(
9	name="Invoice Processing",
10	steps=[
11	WorkflowStepDefinition_Trigger(
12	name="trigger",
13	next=[
14	SimpleNextEntry(
15	step="parse",
16	)
17	],
18	),
19	WorkflowStepDefinition_Parse(
20	name="parse",
21	next=[
22	SimpleNextEntry(
23	step="extract",
24	)
25	],
26	),
27	WorkflowStepDefinition_Extract(
28	name="extract",
29	config=ExtractStepDefinitionConfig(
30	extractor=ExtractorRef(
31	id="ex_abc123",
32	version="latest",
33	),
34	),
35	next=[
36	SimpleNextEntry(
37	step="review",
38	)
39	],
40	),
41	WorkflowStepDefinition_HumanReview(
42	name="review",
43	)
44	],
45	)

1	{
2	"object": "workflow",
3	"id": "workflow_BMlfq_yWM3sT-ZzvCnA3f",
4	"name": "Invoice Processing",
5	"createdAt": "2024-03-21T16:45:00Z",
6	"updatedAt": "2024-03-21T16:45:00Z",
7	"draftVersion": {
8	"object": "workflow_version",
9	"id": "workflow_version_Zk9mNP12Qw4-yTv8BdR3H",
10	"version": "1",
11	"name": "Production v1",
12	"steps": [
13	{
14	"name": "string",
15	"type": "TRIGGER",
16	"next": [
17	{
18	"step": "parse"
19	}
20	]
21	}
22	],
23	"createdAt": "2024-03-21T16:45:00Z"
24	}
25	}

Create Workflow

Authentication

Headers

Request

Response

Errors

Authentication

Headers

Request

Response

Errors