Build a Job Posting Signal → HubSpot ABA Opportunity + Slack Workflow with n8n
Your best-fit accounts are telling you exactly when they're ready to buy — and you're missing the signal. When a target company posts a job for a CMO, VP of Sales, or Head of Revenue, they're announci
Your best-fit accounts are telling you exactly when they're ready to buy — and you're missing the signal. When a target company posts a job for a CMO, VP of Sales, or Head of Revenue, they're announcing a strategic shift: new budget, new priorities, and a new decision-maker who has 90 days to prove they can change things. That is the single highest-intent moment in account-based selling, and almost nobody catches it in time. This guide shows you how to build an n8n workflow that detects those job postings across your target accounts, creates a structured Account-Based Automation (ABA) opportunity in HubSpot, and drops a Slack alert in front of your AE the same hour it happens.
The problem: hiring signals expire faster than your CRM refreshes
Intent data providers sell you "surges" that are weeks old and shared with every competitor on the same platform. Job postings are different. They are public, timestamped, and directly tied to a named person about to control budget. A company hiring a VP of Sales is about to buy sales tooling, rethink outbound, and re-evaluate every vendor relationship the previous leader owned.
The catch is latency. By the time a rep manually checks a careers page, forwards a link to marketing, and someone remembers to log it in HubSpot, the role is filled or the moment has passed. Manual monitoring across 200 target accounts is impossible — that's 200 careers pages, each in a different format, changing daily. You need machine detection, structured enrichment, and instant routing. That's three jobs, and n8n handles all three in one workflow.
The solution: a signal-to-opportunity pipeline in n8n
The workflow has a simple spine: detect → filter → dedupe → enrich → create opportunity → notify. n8n orchestrates each stage with native nodes, so there's no glue code to maintain and every step is observable in the execution log.
At a high level: a Schedule Trigger fires the run on a cadence (every few hours). An HTTP Request node pulls fresh postings for your target accounts from a job data source. A Filter node keeps only the senior revenue roles you care about. A Code node deduplicates against jobs you've already seen so the same posting never fires twice. A HubSpot node checks the company exists and creates a deal (your ABA opportunity) with a "Hiring Signal" source. Finally a Slack node posts a rich alert to the account owner. The whole chain runs unattended and self-documents each execution.
Step-by-step setup with n8n
1. Schedule Trigger. Start with a Schedule Trigger set to an interval expression — every 4 hours during business days is a sensible balance between freshness and API cost. Job postings don't appear by the minute, so polling more often just burns quota.
2. Pull the postings (HTTP Request node). Add an HTTP Request node pointing at your job-signal source — a jobs API, an ATS aggregator, or a scraping endpoint. Pass your target-account domains as a parameter and set the method to GET. Store the API key in n8n Credentials (Header Auth), never inline. Set "Response Format" to JSON and enable "Split Into Items" so each posting becomes its own item flowing down the workflow.
3. Filter for senior revenue roles (Filter node). Add a Filter node with an OR condition group matching the job title against your target patterns: CMO, Chief Marketing Officer, VP Sales, VP of Sales, Head of Revenue, CRO. Use the "contains" operator, lowercased on both sides via an expression like {{$json.title.toLowerCase()}} to avoid case misses. Everything that doesn't match is dropped here, keeping downstream volume clean.
4. Deduplicate (Code node + static data). This is the step most people skip and regret. Add a Code node that builds a unique key per posting — company_domain + job_id — and checks it against a seen-list. Use n8n's workflow static data ($getWorkflowStaticData('global')) to persist the seen keys between runs, or write to a database node if you want durability. Return only items whose key is new, then append those keys to the store. Without this, every 4-hour run re-creates the same opportunity.
5. Match the account in HubSpot (HubSpot node — Search). Use the HubSpot node in "Company: Search" mode, matching on domain. If the company exists, grab its company_id and owner. If it doesn't, branch with an IF node: either create the company or route it to a separate "net-new account" Slack channel so a human decides whether to onboard it. Connect HubSpot with a Private App token stored in Credentials.
6. Create the ABA opportunity (HubSpot node — Create Deal). Add a HubSpot node in "Deal: Create" mode. Set the deal name dynamically: {{$json.company_name}} — {{$json.title}} hire signal. Populate custom properties — hs_deal_source = "Job Posting Signal", a signal_role field with the title, a signal_url with the posting link, and a signal_date. Associate the deal with the matched company ID and assign the owner you pulled in step 5. Set the pipeline stage to something like "ABA — Signal Detected" so these opportunities are reportable as their own cohort.
7. Notify the owner (Slack node). Finish with a Slack node posting to the AE's channel or via DM using the owner's mapped Slack ID. Use Block Kit formatting for a scannable alert: company name and logo, the exact role posted, a link to the job, a link straight to the new HubSpot deal, and a one-line "why now" — for example "They're hiring a VP Sales — outbound strategy is in flux, reach the hiring manager before the role fills." A good alert makes the next action obvious in five seconds.
The benefits: speed, structure, and a repeatable ABA motion
Speed. You move from signal to sales rep in under four hours instead of never. In competitive deals, being the first vendor to reference a leadership change is a genuine edge — it reads as research, not luck.
Structure. Every opportunity lands in HubSpot with consistent properties, which means you can finally measure the motion: how many hiring signals convert to meetings, which roles convert best, and whether CMO hires or VP Sales hires drive more pipeline. Manual logging never gives you that dataset.
Leverage. One workflow watches 200 accounts as easily as 20. Your reps stop doing careers-page archaeology and spend their time on outreach. And because it's n8n, the logic is transparent and forkable — you can clone the workflow for a second segment (say, hiring for "Head of Demand Gen") in minutes.
Common pitfalls to avoid
Skipping deduplication. The number-one failure mode. Without a persistent seen-list, every run recreates deals and spams Slack until reps mute the channel. Build step 4 first, not last.
Filtering too loosely. Matching on "Sales" alone will surface SDR and account-exec listings that carry no strategic signal. Anchor your filter on seniority tokens (VP, Chief, Head of, Director of Revenue) so you only fire on budget-controlling hires.
Hardcoding credentials. Putting API keys or HubSpot tokens directly in HTTP nodes leaks them into execution logs and exports. Always use n8n Credentials with Header Auth or the native OAuth/Private App connectors.
No error branch. Job APIs rate-limit and HubSpot occasionally times out. Turn on "Continue On Fail" for the enrichment nodes and route failures to a Slack "workflow needs attention" channel, so a single bad response doesn't silently kill the run and leave you blind for days.
Owner mapping drift. Slack IDs and HubSpot owners fall out of sync as teams change. Keep a small mapping table (a Set node or a lookup in Airtable/Postgres) and review it monthly, or alerts will route to people who left.
Over-polling. Running every 15 minutes won't make signals appear faster — postings refresh daily at best. It just burns API quota and risks rate limits. Every 3–4 hours captures everything with room to spare.
Build it once and this pipeline quietly compounds: every leadership hire across your ICP becomes a timestamped, owned, actionable opportunity while your competitors are still refreshing careers pages by hand.
Ja construimos isso pra voce
Nao comece do zero. O Job Posting Signal → HubSpot ABA Opportunity + Slack e um workflow n8n pronto para instalar — conecta suas ferramentas em minutos, sem codigo.
Instalar por $79 →
