Templates

Workflow templates give you a head start. Instead of building from a blank canvas, load a template that already has the right nodes configured and connected — then customize it for your use case.

---

Using a Template

From the Workflows List

1. Click Workflows in the sidebar.
2. Click New Workflow.
3. In the creation dialog, click Start from template (instead of entering a name for a blank workflow).
4. Browse the template catalog.
5. Click a template to preview its node structure.
6. Click Use Template.
7. Give the workflow a name.
8. Click Create.

The canvas opens with the template's nodes pre-configured and connected. You still need to:

• Select agents for each Agent node (templates use placeholder agent names)
• Configure trigger settings (webhook secrets, cron expressions)
• Adjust any node labels or expressions for your specific use case

From the Canvas

If you're on a blank canvas (new workflow):

1. Click Templates in the canvas toolbar.
2. Same template browser opens.
3. Select and apply.

Applying to an existing workflow

Applying a template to an existing workflow with nodes will replace the existing nodes. Save your work first, or use a new workflow for the template.

---

Built-in Templates

Template 1: Web Research Pipeline

What it does: Takes a topic as input, searches the web for current information, and produces a structured research brief.

Nodes:

[Manual Trigger] → [Agent: researcher (web_search)] → [Agent: writer (formatter)] → [Output]

Configure:

• researcher: Set to an agent with web_search capability
• writer: Set to any agent with a formatting system prompt

Use cases: Research reports, competitive analysis, topic briefings

---

Template 2: Scheduled Security Monitor

What it does: Runs on a schedule, calls an API or log source, analyzes results, and routes by severity.

Nodes:

[Schedule Trigger] → [Agent: log-fetcher (http_request)] → [Agent: analyzer] 
→ [Branch: severity == high?] 
  → [True: Agent: alerter] → [Output: Alert]
  → [False: Agent: logger] → [Output: Log]

Configure:

• Schedule trigger: Set cron expression and timezone
• log-fetcher: Configure with your log API endpoint in system prompt
• analyzer: Set to security analysis agent

Use cases: Security monitoring, uptime checking, compliance scanning

---

Template 3: Content Production Pipeline

What it does: Takes a content brief (title, keywords, audience), generates a draft, runs it through an editor, and optionally pauses for human approval.

Nodes:

[Webhook Trigger] → [Agent: writer] → [Agent: editor] 
→ [HiL: Approve content?]
  → [Approved: http_request node → POST to CMS] → [Output: Published]
  → [Rejected: Output: Rejected]

Configure:

• Webhook trigger: Generate secret and configure your content management system to post here
• writer: Content writing agent with your brand voice
• editor: Editing agent with your style guide
• http_request node: POSTs the approved content to your CMS API

Use cases: Blog post pipelines, social media scheduling, newsletter generation

---

Saving Your Own Templates

You can save any workflow as a template for reuse within your project:

1. Open the workflow on the canvas.
2. Click Templates in the toolbar.
3. Click Save as Template.
4. Enter a template name and description.
5. Click Save.

Your custom template now appears in the template catalog when creating new workflows (visible to all project members).

Templates are project-scoped

Custom templates are only visible within the project where they were created. To share a template across projects, use Import/Export to export the workflow as JSON and import it into another project.

---

Template Anatomy

When you apply a template, it sets up:

• Nodes with types, labels, and basic configuration
• Edges connecting the nodes correctly
• Input expressions in each node (with placeholder agent names)
• Trigger configuration with sensible defaults

Templates do not include:

• Agent selection (you must pick your agents for each node)
• API keys (referenced by the agent, not the template)
• Webhook secrets (regenerated fresh)
• MCP server connections (project-specific)

---

Import vs. Template

Feature	Template	Import (JSON)
Source	Built-in or saved from project	Exported workflow JSON file
Agent configs	Placeholders (you pick agents)	Copies exact agent references
Customization	Expected — it's a starting point	Optional — can use as-is
Sharing	Within project	Any format, across projects
Expressions	Generic ({{trigger.output}})	Exact expressions from source

For sharing workflows between projects or teams, use Import/Export. For starting points with best-practice patterns, use Templates.

See Import/Export for the JSON export/import workflow.