How to Use n8n with ._Template 71 Company Expansion Outreach

A company that grew headcount 20% in six months and has 10+ open roles is spending money right now — on tools, systems, and people. They are the warmest outbound account you will ever touch, and your SDRs are finding them by hand: scrolling LinkedIn, refreshing Apollo saved searches, guessing at the right VP to email. By the time a rep spots the signal, three competitors already booked the meeting. This article shows you how to detect company expansion signals automatically and drop a fully-contextualized deal into HubSpot every morning — using a single n8n workflow (Template 71: Company Expansion Signal → Apollo + HubSpot Outreach Deal).

The Problem: Expansion Signals Decay in Hours, Not Days

Growth signals are the highest-intent buying trigger in B2B outbound, but they have a brutally short half-life. A company that just closed a Series B or posted 12 engineering roles is a hot account for maybe 72 hours before the entire market piles in. Manual monitoring can't keep pace with that decay, and it fails in three predictable ways:

• Latency. A rep checking Apollo once a day misses the signal that fired at 6 a.m. and was acted on by a competitor by 9 a.m.
• Inconsistent qualification. "Fast-growing" means 15% headcount growth to one rep and 40% to another. Without a hard threshold, your pipeline fills with noise.
• Lost context. Even when a rep finds the account, they still have to identify the decision-maker, pull the email, and write the "why now" hook manually — 15 minutes of work per account that kills throughput.

The result is a pipeline that reacts to expansion instead of getting ahead of it. You need the signal detected, qualified, enriched, and routed before a human is even awake.

The Solution: A Daily Signal-to-Deal Pipeline in n8n

Template 71 turns expansion detection into a lights-out process. Once a day, n8n queries Apollo for companies matching your growth criteria, filters them against a hard expansion threshold, finds the right decision-maker at each qualifying account, merges the company and contact data, and creates a HubSpot deal with a pre-written outreach hook — then posts a Slack alert so your rep sees the account with full context in one glance.

Nothing about this requires custom code or a scraping infrastructure. It's a self-hosted or cloud n8n instance, an Apollo.io API key, a HubSpot key, and a Slack webhook. The entire workflow imports in under a minute and runs on a schedule you control. The strategic win is that qualification logic lives in one place — change your headcount threshold once and every rep is working the same definition of a good account.

Step-by-Step: Building the Workflow in n8n

Here is how the nodes chain together. Import the workflow JSON first, then walk each node and wire in your credentials.

1. Schedule Trigger node. Set it to run daily — 6:00 a.m. in your reps' timezone works well so deals are waiting at the start of the day. Use the "Interval" mode set to days, or a Cron expression like 0 6 * * 1-5 to skip weekends.
2. Apollo Company Search (HTTP Request node). Point a POST request at https://api.apollo.io/v1/mixed_companies/search. Pass your api_key and filter on organization_num_employees_ranges, currently_hiring, and job-posting counts. Add a header Content-Type: application/json and store the Apollo key in n8n Credentials, not inline, so it never leaks into exported JSON.
3. Filter / Code node — expansion scoring. Use a Code node (JavaScript) to compute an expansion score per company: headcount growth over 6 months, active job count, and Apollo intent score. Return only companies above your threshold, e.g. growth6mo >= 0.20 && openJobs >= 10. This is the single most important node — it is the difference between a clean pipeline and spam.
4. Apollo People Search (HTTP Request node). For each qualifying company, POST to https://api.apollo.io/v1/mixed_people/search filtered by person_titles such as ["CEO","COO","VP Operations","Head of Sales"] and the company domain. Return the top match with name, verified email, and LinkedIn URL.
5. Merge node. Combine the company expansion data with the decision-maker record so each item carries both the "why now" signal and the "who to reach."
6. HubSpot node — Create Deal. Use the native HubSpot node with the "Deal: Create" operation. Map the deal into your outbound pipeline stage, set the deal name to the company, and write the expansion signals plus a personalized hook into a custom property (e.g. outreach_context). Associate the deal with the contact record so the rep has the email in place.
7. Slack node. Post to #expansion-signals using Block Kit: company name, growth %, open roles, decision-maker name/title, and a direct link to the HubSpot deal. One message, all context.

Wire the nodes in sequence, run once manually with the Schedule Trigger's "Execute Workflow" button, and confirm a test deal lands in HubSpot before you activate the schedule.

Configuration Details That Matter

A few settings separate a workflow that runs reliably from one that quietly breaks:

• Pagination and rate limits. Apollo paginates results — loop with the page parameter until you've pulled your daily cap, and add a small Wait node between calls to respect Apollo's rate limits. Twenty to fifty qualified accounts per day is a healthy volume.
• Dedup against existing deals. Before creating a HubSpot deal, add a HubSpot "Search" node to check whether the company already exists in an open deal. Skip duplicates so you don't create the same account three times in a week.
• Error handling. Attach an Error Trigger workflow or enable "Continue On Fail" on the HTTP nodes, routing failures to a Slack alert. If Apollo returns a 401, you want to know before your pipeline goes silent for a week.
• Credential hygiene. Store every API key in n8n's Credentials store, referenced by name. Never hardcode keys in HTTP nodes — exported workflow JSON is shareable and keys leak that way constantly.

The Benefits: Speed, Consistency, and Rep Leverage

Automating expansion outreach changes the economics of your outbound motion in three concrete ways.

• You reach accounts while the signal is fresh. A deal created at 6 a.m. from a signal that fired overnight puts your rep first in the inbox, not fourth.
• Qualification is uniform and tunable. Every account in the pipeline cleared the same threshold. When you want to raise the bar, you edit one Code node — no retraining, no drift.
• Reps do the human work only. The workflow hands them a qualified account, a named decision-maker, a verified email, and a "why now" hook. The rep writes one personal line and sends. That's a 15-minutes-to-2-minutes reduction per account, and it compounds across your whole team every single day.

Net effect: more first-touches on higher-intent accounts, with less manual labor and zero signal decay.

Common Pitfalls to Avoid

• Threshold too loose. Setting growth at 10% and open jobs at 3 floods your pipeline with weak accounts and burns rep trust in the automation. Start strict (20%+, 10+ roles) and loosen only if volume is too low.
• Skipping the dedup check. Without it, a company that stays in expansion mode for a month generates a new deal daily. Reps stop opening the Slack channel.
• Trusting unverified emails. Apollo returns some guessed emails. Filter on email_status: "verified" in the People Search step, or route unverified contacts to a separate enrichment path rather than emailing them and tanking your domain reputation.
• No timezone alignment. If your Schedule Trigger runs on UTC but your reps are in PST, deals land at odd hours. Set the n8n instance timezone explicitly and match the cron to your team's morning.
• Ignoring Apollo rate limits. Firing hundreds of people-search calls with no Wait node will get you throttled mid-run, leaving half your accounts un-enriched. Batch and pace.

Get the threshold and the dedup right, and Template 71 becomes a quiet, reliable engine that feeds your reps the market's warmest accounts before their first coffee — every business day, without anyone lifting a finger.