Skip to main content
Eight ready-made flows ship with the builder, four filed under an Outbound tab and four under an Inbound tab. Each is a full graph of blocks that lands on the canvas when you pick it, and you can edit it freely from there. Not all eight reach the gallery, and the last two sections explain which and why.
Where
Outreach→Workflow Builder
Your role needs
Create access to Workflow Builder create-workflows. Admin and Member have it by default.
To create or change
create-workflows to add one, update-workflows to change one, on top of the permission above.
Not listed in the sidebar today; reachable from the surfaces that link to it, and by URL. If you cannot find this in your sidebar, your workspace may have a custom menu configuration. Contact support and we will check it for you.

​
Outbound templates

​
Inbound templates

​
What’s already built into every template

Five of the eight open the same way. If / Else checks whether the lead already has an address, and Find Email looks one up if not. Either way, Verify Email checks it before anything sends, and treats a risky result as good enough to go (see Find & Enrich blocks for what that means). A lead nothing can find an address for, or one whose address comes back invalid, exits the workflow right there instead of reaching a send block with nothing deliverable to send to. Core Outbound Sequence, AI Research Outreach, Email + LinkedIn (on the branch where the invite was never accepted), Website Visitor → Outreach and Inbound Lead Capture all open this way. The other three skip it: Reply Handling and Hot Lead Alert both act on a lead who already reached you, and Meeting → Convert never sends an email at all. Every Send Email, Send Follow-up, Send Reply and LinkedIn message block in these templates already carries a full AI prompt, not a blank one, built around merge variables: {{lead.name}}, {{lead.job_title}}, {{lead.leadCompany.name}} and {{sender.name}} among them. Open any block’s own panel and the prompt is right there to read and edit. Merge variables and lead fields lists every path you can drop into one yourself. On the three email send blocks, Sender defaults to the automatic option, which rotates across all your email accounts. Wherever a reply gets branched by intent, the shape repeats: the AI reads it as interested, an objection or not interested (Reply Handling adds out-of-office), then routes to a tailored Send Reply. An objection that comes back again loops back through that same read rather than dead-ending the lead, and the loop is bounded so it can’t cycle forever. A template disappears whole, not block by block, the moment the workflow engine can’t run something inside it, never because a channel isn’t connected. The builder checks every block a template would drop onto the canvas before it ever shows the card, because a saved workflow carrying one unsupported block would just fail to activate anyway. Two of the eight are held back this way, for two different reasons. Hot Lead Alert is the one nobody can bring back: its trigger, Link Clicked, is not one the engine can enroll a lead from (Triggers reference covers why), so the template built around it never shows. Inbound Lead Capture opens on Form Submitted, which is switched on wherever web forms are, and held back with them wherever they are not, taking the whole template with it.

​
A connected channel is a different kind of gap

A disconnected channel never removes a template from the gallery. Email + LinkedIn shows up on the Outbound tab whether or not a LinkedIn account is connected, and the same goes for the Slack step built into Meeting → Convert and Inbound Lead Capture. Apply any of them and the graph loads and saves fine. What stays blocked is Activate: a block whose integration isn’t connected counts as an error, not a warning, in the toolbar’s validation count, and the button stays disabled until the count of errors is zero. Connect the channel or edit that block out and it clears. Build your first workflow walks through what that count shows and how to read it.

Build your first workflow from a template

Apply Core Outbound Sequence step by step, from the empty canvas to Activate.

Triggers reference

Every trigger a workflow can start from, including the ones no template uses.

Outreach and AI blocks

What Send Email, Send Reply, AI Decision and the rest actually do, block by block.

Connect the forms on your website

Scan your site, map the fields and install the tracked forms Form Submitted starts from.