List Workflow Node Types
GET/api/automation/workflow-nodes
Catalog of every node type available for building workflow graphs. Use the type values here as nodes[*].type when creating or updating a workflow.
settings:readGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Each definition describes the node's category (triggers, actions, logic, ...), its inputs and outputs, the schema of the data it emits (outputSchema), and the settings it accepts (key, type, whether required, and default value).
Three more fields are derived from the engine rather than declared by each node, so they always match what a run does:
preview— what a preview-mode run does with the node:runs(executes for real; it cannot change anything),skipped(never executes; its input passes straight through), orsimulated(never executes; reports what it would have done).mutatesistruewheneverpreviewis notruns.operators— on everyconditions/switch_rulessetting, the complete list of condition operators the engine evaluates. An operator outside this list does not error; it evaluates false.availability— triggers only, computed for the current account:{ "available": bool, "reason": string|null }. A trigger whose event no connected integration publishes (for examplechannel-order-importedwithout a TikTok Shop connection) reportsavailable: falsewith a reason naming the alternative — a workflow on it would publish cleanly and never run.
Request
Responses
- 200
- 401
- 403
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.