Don't build every workflow from scratch. Start from a template to get a fully wired head start, publish your best workflows as templates for the team, and turn form-trigger workflows into in-app fillable forms.
The Templates tab in the Automate hub holds ready-made workflows for common patterns — intake triage, scheduled digests, document ingest, approval routing, and more. A template is a complete, pre-wired graph you can clone and adapt to your own tools and data.
Open Workflows → Templates and find a template that matches what you want to automate.
Cloning a template gives you a fully wired copy on the canvas — every node and connection already in place.
Swap in your integrations, knowledge folders, prompts, and recipients. The structure is done; you just fill in the specifics.
Run validation, fix any flagged nodes, then publish to make it live — exactly like any workflow you built by hand.
When you build a workflow worth reusing, you can publish it as a template so others can start from it. Your workflow becomes a clonable starting point in the Templates library, spreading a proven pattern across the team without copy-pasting.
Creating a workflow from a template makes an independent copy. Editing your copy never changes the template, and updating the template never alters workflows already cloned from it.
A form-trigger workflow renders an in-app fillable form. You define the form's fields in the trigger's inspector; when someone submits the form, the entered values become the workflow's input and the run begins. It's the simplest way to give colleagues a structured way to kick off an automated process — intake requests, support tickets, approval submissions, and more.
Form-trigger workflows appear in the Forms tab, where the rendered form lives and can be shared with the people who need to fill it in. See Triggers for how the form trigger fits alongside the other ways a workflow can start.
You've covered building, triggers, nodes, running, and now templates and forms. Next up in the docs is the Knowledge Base — the documents and websites your AI nodes and agents draw on.