> ## Documentation Index
> Fetch the complete documentation index at: https://help.pipelime.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Workflow templates reference

> The ready-made outbound and inbound flows, what each one does, and why one might be missing from your gallery.

export const Screenshot = ({id, alt, caption, frame = 'browser', url, marks = [], lang = 'en', workspace = 'northwind-outbound'}) => {
  const src = `/images/screenshots/${lang}/${id}.png`;
  const chrome = url ? `app.pipelime.ai/${workspace}${url}` : 'app.pipelime.ai';
  return <figure className={`pl-shot pl-shot--${frame} not-prose`}>
      <div className="pl-shot__frame">
        {frame !== 'bare' && <div className="pl-shot__bar">
            <span className="pl-shot__dots">
              <span className="pl-shot__dot" />
              <span className="pl-shot__dot" />
              <span className="pl-shot__dot" />
            </span>
            <span className="pl-shot__url">{chrome}</span>
          </div>}
        <div className="pl-shot__media">
          <img src={src} alt={alt} loading="lazy" />
          {marks.map(mark => <span key={mark.n} className="pl-shot__mark" style={{
    left: `${mark.x}%`,
    top: `${mark.y}%`
  }} aria-hidden="true">
              {mark.n}
            </span>)}
        </div>
      </div>
      {caption && <figcaption className="pl-shot__caption">{caption}</figcaption>}
    </figure>;
};

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.

<div className="pl-availability">
  <div className="pl-availability__row">
    <div className="pl-availability__label">Where</div>
    <div className="pl-availability__value"><span className="pl-path">Outreach<span className="pl-path__sep">→</span>Workflow Builder</span></div>
  </div>

  <div className="pl-availability__row">
    <div className="pl-availability__label">Your role needs</div>
    <div className="pl-availability__value">Create access to Workflow Builder <code>create-workflows</code>. Admin and Member have it by default.</div>
  </div>

  <div className="pl-availability__row">
    <div className="pl-availability__label">To create or change</div>
    <div className="pl-availability__value"><code>create-workflows</code> to add one, <code>update-workflows</code> to change one, on top of the permission above.</div>
  </div>

  <div className="pl-availability__note">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.</div>
</div>

## Outbound templates

| Template                   | Flow                                                          | What it does                                                                                                                                                                                                                                                                                                                                              |
| -------------------------- | ------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Core Outbound Sequence** | New lead → Verify email → AI + 3 follow-ups → Reply by intent | Verifies the lead has a deliverable address, sends an AI first touch, marks the lead contacted, then follows up three times on a fixed schedule if nothing comes back. Any reply branches into a tailored response.                                                                                                                                       |
| **AI Research Outreach**   | New lead → AI research → Verify & email → Reply by intent     | Has the AI pull a few hooks about the lead's company first and opens with those instead of a generic first line, then the same verify, follow-up and branch-by-intent shape as Core Outbound Sequence, one follow-up shorter.                                                                                                                             |
| **Email + LinkedIn**       | New lead → LinkedIn → Verified email fallback → Reply         | Opens on LinkedIn: view the profile, wait, send a connection note. Accepted, it likes a post and then sends a LinkedIn message. If the invite is never accepted, the flow falls back to the verify-and-email sequence. If the invite is accepted but the message goes unanswered, it switches to email on its own branch, which has no verification step. |
| **Meeting → Convert**      | Meeting booked → Set stage → Notify team → Converted          | The short one: a booked meeting updates the lead's stage, alerts the team on Slack, then marks the lead converted after a pause. No email anywhere in it.                                                                                                                                                                                                 |

<Screenshot id="workflows/templates-reference--gallery-outbound" url="/workflows/new" alt="The Outbound tab of the workflow template gallery, showing Core Outbound Sequence, AI Research Outreach, Email + LinkedIn and Meeting → Convert as a single column of cards, each with an icon, a name and a short flow breadcrumb, with a start-from-scratch row of trigger buttons below the cards" caption="All four outbound templates every time: none of them needs a channel connected to show up here." />

## Inbound templates

| Template                       | Flow                                                           | What it does                                                                                                                                                                                                    |
| ------------------------------ | -------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Reply Handling**             | Reply in → AI intent → Tailored reply                          | Fires when an email reply from the lead comes in, has the AI read intent, then sends the matching response: interested, objection, not interested, or out-of-office.                                            |
| **Hot Lead Alert**             | Link clicked → Alert team → Timely follow-up → Reply by intent | Fires when a lead clicks a tracked link, sets their likelihood-to-convert score high, alerts the team on Slack, and follows up while the intent signal is still fresh. Not currently in the gallery, see below. |
| **Website Visitor → Outreach** | Site visit → AI qualify → Verify & email → Reply               | Fires on a tracked visit that resolves all the way to a lead, has the AI judge fit, then runs the same verify-and-email opening as the outbound templates before chasing a reply.                               |
| **Inbound Lead Capture**       | Form in → Qualify → Verify & email → Reply                     | Fires on a submitted web form, marks the lead contacted, alerts the team on Slack, has the AI judge fit, then verifies and emails. Needs web forms switched on, see below.                                      |

<Screenshot id="workflows/templates-reference--gallery-inbound" url="/workflows/new" alt="The Inbound tab of the workflow template gallery, showing three cards: Reply Handling, Website Visitor → Outreach and Inbound Lead Capture, each with a name and a short flow breadcrumb" caption="Three cards, not four: Hot Lead Alert is missing for the reason below, not because of anything in this workspace." />

## 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](/en/workflows/find-and-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](/en/workflows/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.

## Why a template might not be in your gallery

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](/en/workflows/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](/en/workflows/build-your-first-workflow) walks through what that count shows and how to read it.

## Related

<CardGroup cols={2}>
  <Card title="Build your first workflow from a template" icon="sparkles" href="/en/workflows/build-your-first-workflow">
    Apply Core Outbound Sequence step by step, from the empty canvas to Activate.
  </Card>

  <Card title="Triggers reference" icon="zap" href="/en/workflows/triggers-reference">
    Every trigger a workflow can start from, including the ones no template uses.
  </Card>

  <Card title="Outreach and AI blocks" icon="send" href="/en/workflows/outreach-and-ai-blocks">
    What Send Email, Send Reply, AI Decision and the rest actually do, block by block.
  </Card>

  <Card title="Connect the forms on your website" icon="plug" href="/en/finding-leads/web-forms-connect">
    Scan your site, map the fields and install the tracked forms Form Submitted starts from.
  </Card>
</CardGroup>