Everything after the reply, on autopilot.
A workflow follows each lead on its own: it waits, asks, books, nudges your team on Slack and updates the CRM. No-shows, reminders, referrals, LinkedIn-to-email, follow-ups. Built on a canvas, run one lead at a time.
The glue work a lead-gen agency used to do in Zapier, inside the inbox that already has the reply.
- 50 free credits
- No credit card
- Templates included
Start from the ones agencies ask for most
Each one is a page of its own: the trigger, the steps, what the lead sees and what your team sees.
No-show recovery
Ask on Slack if they joined. A no-show goes back to the agent.
Meeting reminders
Email the lead and the host before the call, on your schedule.
Referral handling
“Talk to my colleague” becomes a Slack alert, a CRM record and a thank-you.
LinkedIn to email
Book on LinkedIn, confirm by email, enrich the gap in between.
No-reply follow-ups
Your own follow-up sequence, with a stop rule for every outcome.
LinkedIn booking
Open with three real times when a lead accepts, follow up until they reply, then answer, collect email and phone, book, and confirm.
8 triggers. 18 steps. Every branch connected.
A step cannot publish until every outcome that matters has somewhere to go, so a reply you did not plan for is never dropped.
- LinkedIn reply
A lead sent a LinkedIn message.
- Email reply received
A lead replied to an email.
- Meeting booked
Booked through Cal.com, Calendly, HubSpot, GoHighLevel, Google Calendar, a form, the agent, or by hand.
- Lead marked no-show
Someone answered No-show, on Slack or in the Unified Inbox.
- No reply after a few days
Your last message got no reply for the number of days you choose, from half a day to 60.
- New lead created
A lead was added in this workspace.
- Lead stage changed
A lead moved to another stage.
- LinkedIn connection accepted On request
A lead accepted the connection request.
- Understand & Reply with Calendar
Writes to the lead with live times from the calendar, answering anything they asked.
SentAgreed a timeNo free timesAsked to waitNot a replyAuto-reply - Follow-up
Send the next LinkedIn message if the lead has not replied.
SentFailed - Send a message
One LinkedIn message, written by AI or taken from a template.
SentFailed - Ask for a detail
Ask the lead for one piece of information on LinkedIn, such as their email or phone.
AnsweredNo answerChanged the time or said no - Send an email
Email the lead from your own mailbox, or notify your team.
SentNo emailFailed - Notify on Slack
Post an internal message.
Posted - Hand back to the agent
The inbox agent apologizes, offers new times, and keeps going until the next meeting.
Done
- Book the meeting
Re-check the slot, then book it.
BookedSlot taken
- Branch
Route on the understanding result: sentiment, kind of reply, do-not-contact, agreed a time, or asked a question. Anything unplanned takes the fallback path.
One path per caseEverything else - Wait
Pause before the next step.
Continue - Set a value
Store something for a later step.
Continue - Ask on Slack
After the meeting ends, ask on Slack if the lead joined.
They joinedNo-show
- Enrich lead
Find a missing email, phone or LinkedIn URL with your own enrichment providers.
FoundNot found
- CRM push
Push this lead with the agent’s CRM mapping.
PushedFailed - Send a webhook
Post the lead and reply to your own system, n8n, Zapier or a dialer.
DeliveredFailed - Client handoff
Text the client from this agent’s handoff settings.
DoneFailed - Set a label
Mark the conversation with a category or label.
Continue - Sequence end
Stop here, with a reason that shows in the run list.
Runs you can actually see
“You will see the path it took on the canvas, each step in order, what it sent, and where it stopped.”
The path, on the canvas
Open any run and see the route it took, step by step: the branch taken, what was sent, the times offered, the details collected, and where it stopped.
Approve from wherever you are
A step can wait for a human. Approve, edit or reject from the app, from Slack, or from the email. Nothing waits longer than 48 hours before taking the failed path.
Retry without double-sending
A failed run keeps its lead. Retry carries on from the step that failed, on the version you have live now, and a message that already went out is never sent twice.
Test on a real lead, send nothing
Run a draft against a real lead and the live agent. Nothing is sent, held or written to the CRM. Then publish.
- Stops on not interested or do-not-contact, when a meeting is booked, or when someone on your side replies by hand
- Workspace limits, 12 messages or 90 days per lead by default
- AI drafts are checked before sending: no links, and no times that are not currently held
- Offered times are held so two conversations never take the same slot
- Saving a live workflow makes a draft. Leads stay on the live version until you publish, and runs under way finish on the version they started on
- One LinkedIn account belongs to one enabled workflow
Do I still need Zapier or n8n?
Not for anything that happens because a lead replied, booked, missed or went quiet. That layer runs here, with the thread and the calendar already in hand.
Runs in Underfive
Workflows- Anything that starts with a reply, a booked meeting, a no-show, a quiet thread, a new lead or a stage change
- Messages to the lead on LinkedIn, emails from your own mailbox, posts to Slack
- Booking, holding and re-checking calendar slots
- Pushing the lead to HubSpot, Close or Attio
- Finding a missing email or phone with your own enrichment accounts
- Handing a lead to anything else with a signed webhook
Still a job for a general automation tool
Zapier, n8n, Make
- Jobs that run on a clock with no lead event behind them
- Triggers from systems Underfive does not listen to
- Spreadsheet and multi-app plumbing that has nothing to do with a lead
A JSON POST over https with the lead and the reply, signed with HMAC-SHA256, de-duplicated by delivery id, retried on timeouts. Built to hand a lead to n8n, Zapier or a dialer when you want to.
Built for a workspace per client
One workflow, every client
A workflow can serve several inbox agents. Each lead runs with its own agent’s calendar, sending account, CRM and voice, so one no-show flow covers every client.
Templates you control
Make a template public, or limit it to the clients you choose. One setting covers all of that client’s workspaces.
Your brand on every email
Under white-label, emails and Slack posts carry your agency’s name and logo, not ours.
Owners and admins publish
Anyone can watch runs. Only owners and admins can edit or publish, per workspace.
Workflows FAQ
What can start a workflow?
A LinkedIn reply, an email reply, a booked meeting, a lead marked no-show, no reply for a number of days you choose, a new lead, or a lead changing stage. Reply triggers can be limited to the labels you pick, such as Referral. A LinkedIn connection being accepted can also start one; ask us to turn that on for your workspace.
Does a workflow send on email or LinkedIn?
Messages to the lead are sent on LinkedIn through HeyReach. Email to the lead is the Send an email step, from the Gmail or Outlook mailbox connected to the workspace. A workflow that starts on a LinkedIn reply can use both. One that starts on an email reply can email, notify, enrich, push to the CRM and send webhooks, but not message on LinkedIn.
What does a step cost?
A message written by AI uses credits. A message taken from a fixed template does not, and neither do Wait, Branch, Slack, label, CRM and webhook steps. Enrichment uses your own provider accounts. A fully templated sequence runs on no credits at all.
What happens when a lead replies in the middle of a sequence?
The run moves to your Branch or Understand & Reply step and the follow-ups stop. A not interested or do-not-contact ends the run and labels the thread.
How is this different from Smart Follow-ups?
Smart Follow-ups is a setting on each inbox agent: one to five attempts, chased automatically. Workflows are sequences you design on a canvas, with your own triggers, timing, templates, branches and Slack, CRM and webhook steps.
Can my clients see or edit workflows?
Workflows belong to a workspace. Owners and admins of that workspace can create, edit and publish; everyone else can watch runs. As an agency you choose which templates each client can start from.
Do I still need Zapier or n8n?
Not for the lead-ops layer: everything that happens because a lead replied, booked, missed or went quiet runs here. Keep a general automation tool for scheduled jobs and for systems Underfive does not listen to, and use the Send a webhook step to hand a lead to it when you need to.
Related reading
Put the no-show check live today.
Pick the template, choose a Slack channel, publish. Your first 50 credits are free.