5 n8n Workflows That Automate Your Entire Outbound Operation
Practical n8n automation recipes that eliminate manual work from your outbound process.
n8n is the secret weapon in our GTM stack. While most teams reach for Zapier or Make for basic automations, we use n8n to build the complex, multi-step workflows that actually move the needle on pipeline. The difference is night and day — unlimited executions, full JavaScript code nodes, and self-hosting that keeps our data private and our costs flat.
Here's the stack we connect through n8n, and the five workflows we run every single day.
Our n8n Automation Stack
Workflow 1: Auto-Enrich New CRM Contacts
When a new contact enters HubSpot, this workflow automatically enriches them via Clay, scores them, and routes them to the right sequence based on their score. No rep touches this — it happens in under 30 seconds.
Workflow 1 — Auto-Enrich New CRM Contacts
Trigger: HubSpot webhook on contact creation.
How it works: The webhook fires on every new contact. n8n sends the contact's email and company domain to Clay for enrichment — job title, company size, tech stack, funding data. A code node then calculates a fit score based on our ICP criteria. If the score is above 70, the contact gets routed to a high-intent sequence in Instantly. Below 70, they go into a nurture drip instead.
Watch out for: Make sure your HubSpot webhook filters out internal contacts and test entries. We added a simple domain blocklist to the first node to prevent enriching our own team members.
This workflow alone saves our SDRs 2+ hours per day of manual research and data entry.
Workflow 2: Bounce Handler
When an email bounces in Instantly, this workflow automatically finds an alternative contact at the same company and adds them to the sequence. No lead left behind.
Workflow 2 — Bounce Handler
Trigger: Webhook from Instantly on bounce event.
How it works: The bounce webhook sends us the failed email address and associated domain. n8n parses the company domain, sends it to Clay to find an alternative decision-maker at the same company, verifies the new email address, and adds them to the same sequence the original contact was in.
Watch out for: Set a limit on how many alternative contacts to find per company (we cap at 2). Without this, you can burn through enrichment credits fast on large companies with many bounces.
We recover roughly 15-20% of bounced leads that would otherwise be completely lost.
Workflow 3: Meeting No-Show Follow-Up
When a prospect no-shows a Calendly meeting, this workflow triggers a personalized follow-up sequence with a new booking link. Timing matters here — you want to re-engage while the intent is still warm.
Workflow 3 — Meeting No-Show Follow-Up
Trigger: Calendly no-show webhook.
How it works: Calendly's webhook fires when a meeting is marked as a no-show. n8n waits 1 hour (you don't want to come across as desperate), then sends a personalized email referencing the missed meeting with a fresh booking link. If there's no response within 24 hours, the contact gets added to a re-engagement sequence with 3 additional touchpoints.
Watch out for: Add a check for whether the prospect rescheduled on their own before the follow-up fires. Otherwise you'll send an awkward "you missed our meeting" email to someone who already rebooked.
This recovers about 30% of no-shows into rescheduled meetings — pipeline you'd otherwise lose entirely.
Workflow 4: Weekly Pipeline Digest
Every Monday morning, this workflow pulls pipeline data from HubSpot, crunches it into a clean digest, and posts it to Slack. The whole team starts the week aligned.
Workflow 4 — Weekly Pipeline Digest
Trigger: Cron schedule — Monday at 8am.
How it works: A cron trigger kicks off every Monday morning. n8n queries the HubSpot API for all deals in pipeline, aggregates them by stage, calculates week-over-week changes, and formats everything into a clean Slack message with deal counts, total value per stage, and deals that moved forward or stalled. The message lands in our #pipeline channel before anyone opens their laptop.
Watch out for: HubSpot's API has rate limits. If you have hundreds of deals, paginate your API calls and add a short delay between requests. We use a code node with a simple pagination loop.
Eliminates the Monday morning "where do we stand?" question entirely. Everyone sees the same numbers.
Workflow 5: Competitor Alert Monitor
This workflow monitors when target accounts start using competitor products and triggers a timely outreach sequence. Displacement campaigns are the highest-converting outreach we run.
Workflow 5 — Competitor Alert Monitor
Trigger: Daily cron schedule.
How it works: Every day, n8n triggers a Clay enrichment check on our target account list, scanning for tech stack changes. A code node compares the current tech stack against our competitor list. When a match is found — say a target account just adopted a competitor's tool — n8n enriches the best contact at that company and triggers a displacement-focused sequence in Instantly.
Watch out for: Tech stack data isn't always real-time. There can be a lag of days to weeks between adoption and detection. Account for this in your messaging — don't say "I noticed you just switched to X" if it might have happened weeks ago.
Displacement sequences see 3-4x higher reply rates than cold outreach because you're reaching out at the exact moment of change.
Why n8n Over Zapier or Make
The economics aren't even close. Here's what you're looking at:
Cost Comparison — Automation Platforms
~$20/mo
VPS cost only
$69+/mo
Professional plan
$16+/mo
Core plan
The self-hosted n8n instance runs all five workflows above (plus a dozen more we haven't covered) for a flat $20/month VPS. On Zapier, the same volume of executions would cost $200-400/month. On Make, you'd hit operation limits within the first week.
Beyond cost, n8n gives us full JavaScript code nodes. That means we can write real logic — scoring algorithms, data transformations, API pagination — without being constrained by a drag-and-drop interface.
Getting Started
All five workflows run on n8n's self-hosted version deployed on a basic VPS. Here's what you need:
- A $20/month VPS — we use Hetzner, but DigitalOcean or Vultr work fine
- Docker — n8n runs as a single Docker container
- Webhook endpoints — set up in HubSpot, Instantly, and Calendly
- Clay API access — for enrichment nodes
- 30 minutes per workflow — each one takes about half an hour to build from scratch
Start with Workflow 1 (CRM enrichment). It has the fastest time-to-value and will immediately show your team what's possible. Once that's running, layer on the others one at a time.