What can start an automation?

Three triggers: a new conversation starting, a lead being captured, and a visitor asking for a human. Each event runs an automation at most once, so a page refresh or a repeated submission never duplicates a delivery.

What actions can an automation run?

Notify your team in the dashboard notification center (optionally also by email or WhatsApp), send an email to any address, send a WhatsApp message to any number, post a message to your connected Slack workspace, or deliver the event to one of your webhook endpoints.

Can I personalize the messages?

Yes. Every text field supports placeholders like {{email}} or {{name}}, filled from the event that triggered the run. A captured lead’s email can become the recipient of a follow-up email, and a handoff request’s message can appear inside a Slack alert.

Can an automation wait before acting?

Yes. A Wait step pauses the run for minutes, hours, or days (up to 7 days) before the next step, for example to send a follow-up email an hour after a handoff request.

What happens when I turn Automations off?

Everything stops immediately. Events that happen while the toggle is off are skipped permanently, and runs paused at a Wait step stop instead of resuming when you turn it back on.

How many automations can I create?

Up to 20 automations per agent, each with up to 25 steps. Every automation keeps a run history for 30 days showing what each step did and why a run failed.

Automations

Agent events,
turned into actions.

A conversation starts, a lead is captured, or a visitor asks for a human, and your automation takes it from there: notify your team, send an email or WhatsApp message, post to Slack, or deliver the event to a webhook. Built on a visual canvas, no code.

Get started free View pricing

Up to 20 automations per agent · 25 steps each · run history kept for 30 days

Each event runs an automation at most once. Never a duplicate delivery.

Follow up on new leads

Automation · 5 steps

Runs the moment the event happens, at most once per event

Brands answering faster, selling more, and supporting better with Fetchply

Fetchply is an AI sales and support agent for any brand: SaaS products, business and service sites, docs, and online stores. It answers pre-sale and post-sale questions across your website, WhatsApp, Instagram, Slack, and email, using only your own pages, products, policies, and documents, then hands the conversation to your team with full context when a person is needed. See what that costs on pricing.

How it works

Three steps from a template to a

No code and no external workflow tool. Turn on the toggle, adjust a template on the canvas, and the automation runs the next time its trigger happens.

Turn on Automations

Open Integrations for your agent and switch the Automations toggle on.

Start from a template

Create an automation from a template and adjust its trigger, conditions, and actions on the canvas.

Save and turn it on

Save the draft, fix anything the issues panel flags, and turn the automation on.

Typical setup time:about 2 minutes

Get started free

Capabilities

Six things Automations handles on its own

Three agent events in, five actions out, with conditions and Wait steps in between. You describe the flow once on a canvas; the automation runs it every time after that.

Follow up on every lead

The moment a visitor shares contact details, the automation sends the email for you. Every text field takes placeholders like {{email}} or {{name}}, filled from the event that triggered the run.

Follow up on new leads

Automation · 2 steps

Trigger

Lead captured

A visitor shares contact details

Done

Action

Send an email

To {{email}} · "Thanks for reaching out"

Done

A captured email can become the recipient.

Alert the team on handoffs

When a visitor asks for a human, ping the people who can answer: a message in your connected Slack workspace, a note in the dashboard notification center, optionally email or WhatsApp too.

Escalation alert

Automation · 3 steps

Trigger

Visitor asks for a human

A conversation is escalated

Done

Action

Post to Slack

#support · "{{name}} needs a human"

Done

Action

Notify the team

Dashboard + WhatsApp

Done

The visitor’s message rides along in the alert.

Pause before the next step

A Wait step holds the run for minutes, hours, or days, up to 7, before the next action. Send the thank-you now and the follow-up an hour later, from the same automation.

Delayed follow-up

Automation · 3 steps

Trigger

Lead captured

A visitor shares contact details

Done

Wait

Wait 1 hour

Then continue with the next step

Waiting

Action

Send an email

To {{email}} · "Still have questions?"

Timing is part of the flow, not a calendar reminder.

Event happensOne runNever repeated

One event, one run

Each event runs an automation at most once. A page refresh, a retried submission, or a double click never duplicates a notification, an email, or a webhook delivery.

Build in draftFix flagged issuesTurn it on

Drafts never run

Build on a visual canvas: drag steps anywhere, branch on conditions, undo and redo freely. The issues panel flags anything broken, and nothing runs until you turn the automation on.

Step by stepKept 30 daysFailure reasons

Every run on record

Run history keeps 30 days of every execution, step by step: what fired, what each action did, and the exact reason whenever a step failed, so nothing disappears silently.

Comparison

Manual follow-up depends on memory. Automations run every time

Your agent already knows when a conversation starts, a lead lands, or a visitor asks for a human. Automations turn that knowledge into the follow-up your team would otherwise do by hand.

Moment	With AutomationsAutomaticRuns the moment the event happens	Manual follow-upSomeone watches the dashboard
New lead follow-up	Email sent the moment the lead is captured	Waits until someone checks the inbox
Handoff alerts	Slack, WhatsApp, or dashboard ping the instant a visitor asks	Escalations sit unnoticed between check-ins
Personalization	Placeholders like {{email}} filled from the event	Copy-pasted names and addresses, typos included
Timing	Wait steps pause a run for minutes to 7 days	Follow-ups depend on someone remembering
Duplicates	Each event runs an automation at most once	Double sends when two people react to the same lead
Visibility	Every run recorded for 30 days, step by step	No trace of what was sent, or when
Setup	A template and a visual canvas, no code	A checklist the team must remember under load

Stop being the follow-up step yourself.

Up to 20 automations per agent, 25 steps each.

Create your first automation

How do Automations work on a Fetchply agent?

An automation is a flow you draw once on a visual canvas: a trigger, optional conditions, and the actions that follow. Three agent events can start a run: a conversation beginning, a lead being captured, or a visitor asking for a human. From then on, every matching event starts the flow, fills your placeholders from the event data, and works through each step, pausing at Wait steps for up to 7 days when you want the follow-up later rather than now.

Drafts never run, the toggle stops everything instantly, and 30 days of run history show what each step did. Read the setup documentation, pair it with webhooks to reach your own systems, or check pricing.

Escalation follow-up

Run · started 2 minutes ago

Trigger

Visitor asks for a human

A conversation is escalated

Done

Condition

Outside business hours?

time · matches schedule

Done

Action

Send an email

To {{email}} · "We’ll reply first thing tomorrow"

Done

Wait

Wait 12 hours

Resumes when the wait elapses

Waiting

Action

Notify the team

Dashboard notification center

Every step recorded in run history for 30 days

What makes it different

Built to run unattended, safely

One event, one run. Always.

Each event runs an automation at most once, guaranteed. A refreshed page, a retried form, or a replayed event never sends the email twice or pings the team again. When you turn Automations off, everything stops immediately: events that happen while it is off are skipped permanently, and paused runs stop instead of resuming later.

Edit without fear.

Drafts never run, so you can drag steps around, branch on conditions, and undo or redo freely while the automation stays safely off. The issues panel flags anything incomplete before you go live, and 30 days of run history show exactly what each step did, with the reason whenever a run failed.

Answers before your first automation

Short answers for teams weighing the Automations integration.

Let your agent
handle the follow-up.

Turn on the toggle, pick a template, and your first automation is live in about two minutes.

Start free

Agent events,
turned into actions.

Up to 20 automations per agent · 25 steps each · run history kept for 30 days

Each event runs an automation at most once. Never a duplicate delivery.

Brands answering faster, selling more, and supporting better with Fetchply

Moment

With AutomationsAutomaticRuns the moment the event happens

Manual follow-upSomeone watches the dashboard

New lead follow-up

Email sent the moment the lead is captured

Waits until someone checks the inbox

Handoff alerts

Slack, WhatsApp, or dashboard ping the instant a visitor asks

Escalations sit unnoticed between check-ins

Personalization

Placeholders like {{email}} filled from the event

Copy-pasted names and addresses, typos included

Timing

Wait steps pause a run for minutes to 7 days

Follow-ups depend on someone remembering

Duplicates

Each event runs an automation at most once

Double sends when two people react to the same lead

Visibility

Every run recorded for 30 days, step by step

No trace of what was sent, or when

Setup

A template and a visual canvas, no code

A checklist the team must remember under load

How do Automations work on a Fetchply agent?

Agent events,turned into actions.

Brands answering faster, selling more, and supporting better with Fetchply