Skip to main content
Templates are pre-built flow blueprints. They have the same shape as a flow definitioninputs, variables, steps, webhooks — plus a category and tags for browsing. The template endpoints are public: no authentication required.

Browse templates

Filter by status or category:
Fetch one template in full:
The response carries everything a definition needs: name, description, category, tags, version, status, inputs, variables, steps, and webhooks.

Instantiate a definition from a template

Templates are read-only — to use one, copy its shape into a new definition of your own via POST /flows/definitions. Take the template’s inputs, variables, steps, and webhooks, then supply your own name and status:
The new definition is yours to edit freely — name your own credential on each task, adjust parameters, and re-PUT as needed. Changes to the definition never affect the template.
Most templates that call external platforms leave the task’s credential unset. Create a credential first and set it on each task before activating.
Set "status": "draft" (or omit status) if you want to review and edit before the flow becomes triggerable — only active definitions can be triggered.

Next steps

Build your first flow

Author a definition from scratch instead.

Flow definitions

Every field of the definition shape, explained.