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

# Flow library and AI

> Start from a ready-made recommended automation, or describe what you want and have Senderz build the whole thing on the canvas.

You do not have to build an automation from an empty canvas. Senderz gives you two shortcuts: a library of ready-made automations you can take as-is, and an AI that turns a plain description into a real connected automation.

Both produce an ordinary draft automation. Nothing is scheduled, nothing is sent, and nothing changes until you finish the content and publish it yourself.

## Recommended flows

The **Automations** page opens on a short overview and a **Recommended flows** gallery until you have created your first automation. After that, the gallery moves into the **New automation** panel under the heading **Start another flow**, and **Browse library** takes you to the full library page.

Each card shows the automation's name, what it needs, the channels it uses, and a small diagram of the actual steps. That diagram is generated from the same definition the button builds, so what you see on the card is exactly what you get.

**Use template** creates the automation as a draft in your workspace and opens it in the editor.

### The six starters

<AccordionGroup>
  <Accordion title="Welcome Series (Email)" icon="user-plus">
    Trigger: **Added to list**. Three emails over roughly a week: a welcome,
    then your story after 3 days, then best sellers after another 4. Marked
    **Popular**.
  </Accordion>

  <Accordion title="Welcome Series (SMS)" icon="comment-sms">
    Trigger: **Added to list**. A short two-step sequence: a welcome text, then
    a reminder 2 days later.
  </Accordion>

  <Accordion title="Abandoned Cart" icon="cart-shopping">
    Trigger: **Added to cart**. Waits an hour, sends a first email, texts a
    reminder 23 hours later, then a last-chance email a day after that. Uses
    both email and SMS. Marked **Popular**.
  </Accordion>

  <Accordion title="Browse Abandonment" icon="eye">
    Trigger: **Viewed product**. Waits 2 hours and follows up by email, then
    sends a second email the next day.
  </Accordion>

  <Accordion title="Post-Purchase Thank You" icon="bag-shopping">
    Trigger: **Placed order**. Thanks the customer an hour after they order,
    then asks for a review 14 days later.
  </Accordion>

  <Accordion title="Shipping Updates" icon="truck">
    Trigger: **Fulfilled order**. Emails the customer when the order ships,
    then sends a delivery nudge by SMS 3 days later. Uses both email and SMS.
  </Accordion>
</AccordionGroup>

### The library page

**Browse library** opens the full list. Filter by channel with **All**, **Email**, **SMS** and **Push**, or search by name and description.

The cards behave the same as the ones on the Automations page.

<Warning>
  A starter gives you the shape, not the words. Its message steps arrive as
  **drafts** with no template attached, so the automation would enrol contacts
  and send nothing if you published it as-is. Open each message step, add
  content, and set it to Live. Publishing offers to set them all live for you
  once they have content.
</Warning>

Everything else about a starter is a normal automation. Change the trigger, add or remove steps, adjust the wait times, add an exit rule. Nothing about it is locked.

## Generate with AI

The sparkle button in the top corner of the canvas opens the AI flow agent. Describe the automation you want in plain language and it proposes complete plans you can approve.

<Steps>
  <Step title="Describe it">
    Write what you want, for example "abandoned cart recovery with email then
    SMS after 2 hours". Anything shorter than 5 characters is refused.
  </Step>

  <Step title="Read the proposals">
    You get several plans back, each with a name, the trigger it would use, a
    short explanation of why, and the steps it would build.
  </Step>

  <Step title="Refine, if you want">
    Write a follow-up such as "add SMS after 2 hours and skip the discount
    email" and press **Revise plan**. The agent reworks the plans with your
    change applied.
  </Step>

  <Step title="Approve and apply">
    **Approve and apply** builds the whole automation on the canvas and renames
    the automation after the plan. Undo in the header reverses it if you change
    your mind.
  </Step>
</Steps>

### What the AI can build

A proposal is a real, connected automation, not an outline.

| Part       | What a proposal can contain                                                             |
| ---------- | --------------------------------------------------------------------------------------- |
| Triggers   | Up to 4 entry triggers on one automation, combined so any one of them lets a contact in |
| Steps      | Between 2 and 14 steps after the trigger                                                |
| Step types | Wait, Email, SMS and Push                                                               |
| Branching  | One conditional split, with up to 6 steps on each side                                  |

Email steps come back with a subject line and preview text already filled in. Every step is named, and wait steps carry their real duration.

<Warning>
  Message steps from an AI proposal are **drafts** with no template attached,
  exactly like the library starters. The proposal gives you the sequence and
  the subject lines. You still write the message, set each step to Live, and
  publish. Nothing reaches a customer before you do.
</Warning>

### What it does not do

* It never publishes, schedules or sends anything.
* It cannot place the data steps: Webhook, Update in list, Update user properties, Internal team notification and Grant points are yours to add afterwards.
* It cannot place an A/B test step.
* It does not set your audience filter or exit rules. Open the trigger setup panel and set those yourself.
* Applying a plan **replaces** whatever is currently on the canvas. On an automation you have already built, apply to a fresh one instead, or undo straight away.

### Continue in AI chat

**Open AI chat** moves the conversation into the full assistant, carrying your prompt and the name of the automation you have open. Use it when you want to talk through the approach rather than pick between finished plans.

<Info>
  The AI features run on your own AI provider key. If none is configured, the
  panel says so and offers a **Fix AI key** shortcut. See [AI
  provider](/en/integrations/ai-provider) for how to set one up.
</Info>

## Starting from an automation you already have

If something in your workspace is already close to what you need, copy it instead.

**Duplicate** on any row's menu in the Automations list copies the whole thing: every step, the connectors between them, the audience filter and the exit rules. The copy is created as a draft named after the original with `(copy)` appended, and it never inherits Live status.

This is usually the better option when you want the same sequence for a different audience. Duplicate it, then change the audience filter on the copy.

## Which one to use

<CardGroup cols={2}>
  <Card title="Use a recommended flow" icon="star">
    You want one of the standard e-commerce automations and you want the
    timings to be sensible defaults you can adjust.
  </Card>

  <Card title="Use AI" icon="wand-magic-sparkles">
    You have something specific in mind that no starter covers, and you would
    rather describe it than place a dozen steps by hand.
  </Card>

  <Card title="Duplicate" icon="copy">
    You already have an automation that works and you need a variant of it.
  </Card>

  <Card title="Start from scratch" icon="pen-ruler">
    You know exactly what you want, or the automation is mostly data steps
    rather than messages.
  </Card>
</CardGroup>

Whichever you pick, the finishing work is the same: set up the trigger, write the content, set the message steps live, and run a test before you publish. See [Publishing and monitoring](/en/messaging/flows/publish-and-monitor).