Skip to main content
POST
Create Workflow

Authentication and permissions

Token requirements: User-based token (OAuth) or Organization-scoped API key or Team-scoped API key. Send a bearer access token for one of these identities. The permissions and resource restrictions below also apply.
Permissions joined by + are all required; or separates alternatives. Full-access keys still cannot call endpoints marked unsupported. Team keys must allow every team checked by the request. OAuth access depends on the user’s roles and resource access.

Authorizations

Authorization
string
header
required

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

Body

application/json
teamId
string
required

The ID of the team.

name
string
required

The name of the workflow.

content
string
required

The content/code of the workflow.

description
string

A description of the workflow.

requireFormConfirmation
boolean | null

Whether the workflow requires form confirmation (optional).

isPublished
boolean | null

Whether to publish the workflow after creation (optional).

tagIds
string[]

The IDs of the tags to associate with the workflow.

showInServiceCatalog
boolean | null

Whether to list this workflow in the Service Catalog (optional). When omitted, the workflow is not listed.

serviceCatalogDescription
string | null

Optional description shown at the top of the Service Catalog run form.

package
string | null

The access package, by name, whose connections this workflow's runs may use. Omit it, or send an empty string, to place the workflow in the team's default package. Names match case-insensitively; an unknown name is rejected. Ignored for teams without access packages.

Response

200 - application/json

Success

data
data · object

The created workflow.

integrationAccessFindings
IntegrationAccessFinding · object[]

Advisory reconciliation of the saved content against the version's package. Always empty when the team is not on Integration Access.