7 Make Automations Every Cold Email Team Should Run
Seven no-code Make workflows that connect your cold email platform, CRM, Slack and LinkedIn outreach, so hot leads never sit in an inbox and nobody gets contacted twice.
By the SageLift team, · 6 min read
Disclosure: Some links in this article are referral links. If you sign up through them, SageLift may earn a commission at no extra cost to you.
Most cold email teams lose deals in the gaps between tools. A prospect replies "sounds interesting" on a Friday afternoon, the reply sits in the sending tool's inbox, and by Monday the moment has passed. Or a prospect books a call, but the LinkedIn sequence keeps sending them messages.
Make fixes these gaps. It's a visual, no-code automation platform: you connect apps, choose a trigger, and Make carries the data from one tool to the next. Here are seven workflows worth building, roughly in order of impact.
How Make works in 60 seconds
- A scenario is one automated workflow.
- Each scenario starts with a trigger, such as a webhook from your sending tool or a new row in a sheet.
- Modules are the actions: create a CRM deal, send a Slack message, update a lead.
- Filters decide which records continue, and routers split one flow into several paths.
Most cold email platforms, including Instantly, Smartlead and PlusVibe, can send webhooks when something happens (a reply, a status change, a bounce). That webhook is usually the starting point.
1. Interested reply → CRM deal + team alert
The problem: positive replies sit unnoticed in the sending tool.
The workflow:
- Trigger: your sending platform marks a lead as interested (via webhook).
- Search the CRM for the contact; create it if it doesn't exist.
- Create a deal or opportunity in the first pipeline stage, with the reply text in a note.
- Post a Slack or email alert to the person who handles replies, with a link to the conversation.
Use Close for inside sales teams or GoHighLevel for agencies. This one scenario usually pays for the whole automation setup.
2. Meeting booked → stop all outreach
The problem: a prospect books a call, then receives follow-up email number three and a LinkedIn message. It looks careless.
The workflow:
- Trigger: a meeting is booked in your calendar tool or CRM.
- Find the lead in your sending platform and pause or remove them from every active campaign.
- Do the same in your LinkedIn tool.
- Move the CRM deal to "Meeting booked".
If you run LinkedIn outreach with HeyReach, its native integrations with Instantly and Smartlead can handle part of this, and Make covers the rest.
3. "Not now" replies → a follow-up task in 90 days
The problem: "Reach out next quarter" replies are some of the warmest leads you'll get, and almost nobody follows up.
The workflow:
- Trigger: a reply is labeled "not now" or "later" in your sending tool.
- Create a CRM task due in 60–90 days, assigned to the right person, with the original reply attached.
- Tag the contact so they're excluded from new cold campaigns until then.
4. Unsubscribe and do-not-contact sync
The problem: someone asks not to be contacted, but they're still in another campaign, another client workspace or a LinkedIn sequence.
The workflow:
- Trigger: an unsubscribe or "remove me" reply in any sending tool.
- Add the email (and optionally the whole domain) to a central do-not-contact list, such as a Google Sheet or a CRM field.
- Add it to the blocklist in every sending platform you use.
- Remove the person from LinkedIn campaigns.
This protects your reputation and helps you respect opt-out rules in the markets you email.
5. New leads → verify → into the right campaign
The problem: lists get uploaded by hand, unverified, into whichever campaign someone remembers.
The workflow:
- Trigger: a new lead list lands in a Google Sheet, or a saved search in Apollo returns new contacts.
- Send each email through your verification tool and drop invalid or risky ones.
- Check the do-not-contact list from workflow 4.
- Use a router to send each lead to the right campaign by segment (industry, title or region).
6. No email reply → LinkedIn touch
The problem: some prospects simply prefer LinkedIn.
The workflow:
- Trigger: a lead finishes an email sequence with no reply.
- Look up their LinkedIn profile URL (from your lead data).
- Add them to a LinkedIn campaign in HeyReach with a short connection request.
Keep the LinkedIn message different from the emails; don't just paste the same pitch.
7. Daily or weekly reporting digest
The problem: nobody checks dashboards consistently.
The workflow:
- Trigger: a schedule, such as every weekday at 9 AM.
- Pull yesterday's numbers from your sending platform's API: emails sent, replies, positive replies, bounces.
- Write them to a Google Sheet for history.
- Post a short summary to Slack, and flag anything unusual, such as bounces above 2% or a sudden drop in replies.
Tips for reliable scenarios
- Test with one record first. Run the scenario once on a single test lead and check every app it touches.
- Filter early. Make charges by usage, so put filters near the start to stop irrelevant records before they use more steps.
- Add error handling. Use Make's error handlers to retry, or to alert you when an app's API is down, instead of failing silently.
- Don't duplicate. Always search for an existing contact before creating a new one.
- Name things clearly. "Interested reply → Close deal + Slack" beats "Scenario 7" six months later.
What to build first
If you only build two scenarios, build #1 (interested reply → CRM + alert) and #4 (do-not-contact sync). The first protects revenue, the second protects reputation.
For the full picture of how these tools fit together, see How to Build an AI Cold Email System. If you want the sending infrastructure and tools set up for you, look at SageLift's Machine Setup or Campaign Management.
FAQ
Is Make better than Zapier for cold email?
Both work. Make's visual builder, routers and pricing tend to suit multi-step workflows with branching, which is common in outbound.
Do I need developer help?
Usually not. If a tool has no Make app, its webhooks and Make's HTTP module cover most cases, and that's the most technical part.
Can these automations hurt deliverability?
Not directly. They run after emails are sent. In fact the do-not-contact sync helps, because it keeps people who opted out from receiving more emails.