Reply before you've even seen the request.
An automation is a script: when a form comes in, reply right away; if the person hasn't reacted, follow up two days later; notify me in every case. You write it once, it works every night.
"Answer requests, follow up and remind, without thinking about it." Automations are part of the PRO plan (the 30-day trial includes them). Every automation has three states: Draft (a sketch, nothing runs), Active, Paused.
An automation reads top to bottom: a trigger (what starts it), steps (what it does, in order), and sometimes conditions that open two paths, "If yes" and "If no". The Add a step button inserts and wires the step on its own: no canvas to draw, no arrows to connect.
Where to start #
The Automations page offers four ready-to-review templates: "Instant reply + follow-up", "Date reminder", "Confirmation + deposit", or a blank page. A template opens in the guided editor: the script is already assembled, your text replaces the suggestions.
"Add a step" connects the next step, the yes / no paths split on their own
What triggers an automation #
| Trigger | When it fires |
|---|---|
| Form submitted | A form is submitted: any of your forms, or the one you pick on the page of your choice. |
| Button or link clicked | A visitor clicks a specific button or link. |
| Appointment requested | Someone requests an appointment through a Booking block. |
| Order placed | An order is placed (shop). |
| Payment received (Stripe) | A payment is collected via Stripe. |
| Still no answer after X h | The person hasn't reacted for X hours: the follow-up engine, unless follow-ups have been stopped. |
| Event date approaching | Seven days before an event date. |
| Event date passed | The day after an event date. |
What an automation can do #
| Step | What it does |
|---|---|
| Email the client | Writes to the contact in your name (your address as reply). Ready-made texts: "Instant reply", "Follow-up", "Date reminder", "Confirmation + deposit", or your own text. Options: attach the event's calendar file (.ics), and insert the deposit link from your Stripe. Recipient: the contact, or you. |
| Notify me by email | The alert in your inbox: subject "New request: [first name]", with a reminder: reply from your inbox and it reaches the contact; already handled? The stop link cuts the follow-ups. |
| Notify me on Slack, Discord or Telegram | The same alert, but in your messaging app: a Slack webhook address, a Discord channel, a Telegram bot, or an ntfy topic. Paste the address and the step sets itself up. |
| Add a tag / Set status | Sorts the request in your audience: a "followed up" tag, a "handled" status. |
| Send webhook | For everything else: a free-form address and body, with contact fields you can insert (email, first name, phone, message, page). |
| Wait | The tempo: a delay before the next step, with a "business days only" option. |
| Check a condition | The branch point: see the next section. |
A script holds at most 20 steps: room to reply, follow up, notify and sort, without becoming a maze.
Branches #
A condition tests one thing: "have the follow-ups been stopped?", "does the city field contain Lyon?". It opens two labeled paths, If yes and If no: the script follows the true one. That's how a follow-up switches off cleanly: "Wait 2 days", then "Check: follow-ups stopped?"; yes, everything stops there; no, the follow-up goes out.
Removing a step re-wires the script automatically: what came before connects to what comes after. A condition whose two paths aren't empty can't be removed: empty its branches first. Shared destinations show as continuation links: two paths that land on the same next step.
Three complete examples #
- The salon's instant reply
Trigger: form submitted. Step 1: email to the contact ("Thank you for your request, I'll reply before this evening"). Step 2: a Telegram notification for you. Result: every request gets a reply within a minute, and you're notified in the right place.
- The quote follow-up
Trigger: form submitted. An instant reply, then Wait 2 days, then a condition ("follow-ups stopped?") and, if no, the follow-up email: "Your quote is waiting, any questions?". If the person has replied and clicked the stop link, nothing goes out.
- The confirmation with deposit
Trigger: appointment requested. A confirmation email with the calendar file attached and the deposit link from your Stripe; if the client doesn't pay, a follow-up 24 hours later reminds them. The appointment confirms itself.
What happens when it fails #
A failed email or notification doesn't give up: the step is automatically retried after 5 minutes, then 30 minutes, then 2 hours. If it fails again, the script stops with an error and you receive one alert email per automation per day: "a step didn't complete, check its settings and run the test again". The activity log shows every run, its errors and its stops.
Guardrails protect your contacts: only emails actually sent count toward your monthly email cap (500 by default, raised with the plan); a request whose follow-ups are stopped receives nothing more; and finished scripts leave the log after 90 days to keep it readable.
Test and activate #
The Test workflow button plays the script on a real request, without waiting for the trigger: emails go out (to you, as a test), notifications arrive, conditions get evaluated. Fix what's wrong ("Fix the errors shown on the canvas before activating"), then switch the state from Draft to Active. The automations list shows how many times each one ran; the log keeps the last 20.
Every automatic email carries the follow-up stop link: if the person has already replied, they'll never hear from this script again. The "Stopped" badge on the entry in your data confirms it. Your contacts are in charge, in short.
Frequently asked questions #
How many automations can I run?
As many as your plan allows: the screen tells you when the limit is reached, and the Agency plan carries the most. Each automation is independent: one per form, one per event, that's the clearest way to review them.
Do automatic emails come from my address?
They go out in your page's name, and replies come back to you: at your account address, or at the reply address set in your account. The conversation always continues in your inbox.
Can I build an automation without the guided editor?
The editor is guided on purpose: no free canvas, no zoom. It's the opposite of an engineer's tool: every step inserts itself wired, every text offers a ready-made version, and the test button plays the whole thing before activation.