| Track | Best For | Where It Appears |
|---|---|---|
| Composable Workflows (v2) | New automation built from a graph of blocks | Workflows -> Create Composable |
| Template Workflows (legacy) | Existing prebuilt automations and older Paragon/manual workflows | Workflows -> Create from Template |
Use Composable Workflows for new work. Legacy template workflows still appear on the Workflows list during the migration period and can continue running alongside v2 workflows.
What a Composable Workflow Is
A composable workflow is a saved graph:- One trigger block starts the run.
- Data blocks fetch calls, transcripts, summaries, signals, search results, web pages, or HTTP responses.
- Logic blocks evaluate conditions, ask an LLM, format output, or roll up lists.
- Action blocks send webhooks, post to Slack, add calls to folders, or apply tags.
{{get_summary.summary}}, or a webhook body can combine a call title, transcript, and generated LLM answer.
How Runs Work
Trigger
A workflow starts from a call-completed event, extracted signals, a single signal, a manual run, a schedule, or a test run from the editor.
Resolve Inputs
BuildBetter resolves each block’s config from literals, upstream references, and template strings.
Execute Blocks
The engine runs the graph in dependency order. Condition blocks route only the matching branch.
Block Catalog
Triggers
Call Completed, Signals Extracted, Signal Created, Manual Trigger, Schedule.
Data and Search
Get Call, Transcript, Summary, Signal, Participants, Call Signals, Search Calls, Search Signals, HTTP Request, Exa Search, Firecrawl Scrape.
Logic
Condition, Has Content, String Match, Ask LLM, Format Output, Format List.
Actions
Send Webhook, Send to Slack, Add to Folder, Add Tag.
Common Patterns
Send a Call Summary to Slack
Use Call Completed -> Get Call Summary -> Send to Slack. The Slack block uses the connected Slack workspace and channel picker, so you do not need to build a webhook just to post a message.Route Feature Requests
Use Signals Extracted or Signal Created with Search Signals or Get Signal, optionally add a generated signal filter, then post a digest to Slack or send the payload to a webhook.Create a Weekly Digest
Use Schedule -> Search Calls or Search Signals -> Format List -> Send to Slack or Send Webhook.Replace a Legacy Webhook Template
Start from a composable template such as Send Transcript to Webhook, Send Full Call Data to Webhook, or Conditional Summary to Webhook, then adjust the payload and conditions in the editor.What’s New in v2
Multi-step graphs: Workflows are no longer limited to a single condition and action.
Scheduled workflows: Use a Schedule trigger with a cron expression and timezone.
Native Slack action: Pick a Slack channel directly from connected resources.
Run history: Inspect real and test runs with per-node details and errors.
AI-assisted editing: The workflow chat panel can build, edit, explain, and debug the current graph.
Getting Started
Test Before Enabling
Use Test in the editor. Test runs execute real side effects, so point webhooks and Slack messages at safe destinations first.
Learn More
Creating Workflows
Build a v2 workflow by hand or from a template.
Workflow Automation
Runtime behavior, triggers, block categories, run history, and limits.
Workflow AI Assistant
Use the embedded chat panel to edit and debug workflow graphs.