Decide what happens next, once. Echo does it every time.
A form sign-up, a reply, a target account on your pricing page, an action done: pick the moment, add the steps, switch it on. Echo sends the welcome mail to people who opted in, waits, tells Slack, updates HubSpot or Attio, creates and assigns the follow-up, and calls any other tool through a webhook, Zapier or n8n.
A trigger, a condition, a few steps
Pick what starts it, narrow it down if you like (only the newsletter form, only tier 1 accounts, only pages with “pricing”), then list the steps in order. Texts fill themselves in with the lead's name, the company or the page. Start from a ready-made playbook or from scratch; no flowcharts to draw.
- Nine triggers across forms, replies, visits, accounts, actions and campaigns
- Waits of minutes, hours or days
- A test run with made-up data before you switch it on
Every run, step by step
Each run shows what every step did: the mail that went out, the Slack post, the contact in HubSpot, the action and who got it. A step that fails is tried again three times and then shows its error, so nothing fails silently. Stop a run that's still waiting with one click.
- Only people who opted in are ever emailed
- Unsubscribes and bounces are respected everywhere
- A playbook's own actions never start another playbook
And everything else: webhooks, API, Zapier, n8n
Every event can also go to any address as a signed webhook. An API key with the scopes you choose lets your own code, Zapier or n8n read and add leads and actions, pull AI visibility numbers and run playbooks. The developer docs have every route.
- Signed deliveries, retried for hours
- Keys per workspace, with read or write per area
- Zapier and n8n subscribe and unsubscribe by themselves
Works with
All integrations- SlackNew actions, wrong facts and the Monday summary, with buttons.
- HubSpotContacts, deals and revenue by source; leads in step.
- AttioLeads become people, replies become notes, deals feed your pipeline.
- ZapierEcho's events as Zap triggers; add leads and actions and run playbooks from any Zap.
- n8nThe Echo node and the Echo Trigger for your n8n workflows, cloud or self-hosted.
- Cal.comYour booking link in a playbook's welcome mail.
- HubSpot meetingsYour HubSpot scheduling page in a playbook's mail.
Questions, answered.
Can a playbook email anyone?
No. Email steps only reach leads who opted in: form sign-ups who confirmed their email, or people you imported and confirmed agreed. Anyone who unsubscribed, bounced or complained is skipped, and the run log says so.
How many runs are included?
1,000 runs a month on Starter, 5,000 on Growth and 20,000 on Pro, across all brands. Test runs don't count. Mails a playbook sends count toward the plan's email campaign mails.
Do I need Zapier or n8n?
No. Playbooks cover the common steps inside Echo. Zapier, n8n, webhooks and the API are there for the tools Echo doesn't connect to itself.
What if a step fails?
Echo tries it again three times, a few minutes apart. If it still fails, the run log shows the error and the next steps still run.