Endpoint
application/jsonAuthentication:
Authorization: Bearer <accessToken> header required.
Request Body
string
required
A human-readable display name for the workflow. This name appears in the dashboard and in list/get responses to help you identify the workflow at a glance.
object
required
The complete workflow graph, containing all nodes and the edges that connect them.
Example Requests
The two examples below show the most common workflow patterns. The first uses aFILTER node for pure logic-based row selection. The second delegates selection and message composition to an AI node.
- FILTER Workflow
- AI Workflow
This workflow loads a customer list, keeps only rows where Full request body:
rating is greater than 4, and sends a thank-you email to each qualifying customer — no LLM call required.Response
A successful request returns HTTP201 Created with a JSON body representing the saved workflow. Record the id field — you will use it as workflowId when running, updating, or deleting the workflow.
string
The unique identifier assigned to your workflow by Flowmatic. Use this value as the
workflowId path parameter in run, get, and delete requests.string
The display name you provided in the request body.
object
The full graph definition as saved, including all nodes and edges exactly as you submitted them.
string
An ISO 8601 timestamp indicating when the workflow was created (e.g.,
"2024-08-15T10:30:00.000Z").