LEAD GENERATION
Alert Sales in Slack When a Target Account Spikes Its Open Roles
Tracks open-req counts per target account over time and posts a Slack alert the moment a company's hiring surges past your threshold, with the new roles listed.
How it runs
The automated pipeline, trigger to output.
- TriggerRecurring schedule fires
- ActionCount open roles per account via ApifyApify
- ActionRead prior headcount snapshotPostgres
- LogicFlag accounts past surge threshold
- ActionWrite updated snapshotPostgres
- OutputPost surge alert to SlackSlack
What it does
A sudden jump in open roles means a team is scaling and budget is moving. This workflow counts each target account's live job postings on a schedule, compares against the prior snapshot, and fires a Slack alert when a company crosses your surge threshold — so reps strike during the buildout, not after.
When to use it
Use it when team expansion is your trigger and timing matters. Best for selling enablement, tooling, headcount-driven services, or anything where 'they're growing fast' opens a door. Pairs well with a list of named accounts you already prioritize.
How it works
- 1A schedule runs the check (for example, every six hours).
- 2An Apify actor counts current open roles for each target account from its careers page.
- 3The count is compared to the last stored snapshot for that company.
- 4A threshold step flags accounts whose open-req count jumped past your surge rule (absolute or percentage).
- 5The current count is written back to the snapshot store for the next comparison.
- 6A formatted alert with the company, delta, and new roles posts to the sales Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect ApifyActors, scrapers, datasets.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Lead Generation workflows
Manual Brave keyword sweep into an Airtable research board
On demand, sweeps a topic across Brave Search, clusters the results by buying stage with an LLM, and writes a deduplicated research board to Airtable with company, source URL.
Fast-track hot webinar leads into HubSpot and ping the rep on Slack
After a webinar, identify attendees whose poll answers signal high purchase intent, create or update their HubSpot contact with a lead score.
Webhook-triggered Brave rising-keyword check into a Notion trend queue
When an external trend or alert tool fires a webhook with a keyword, checks Brave for current intent volume and freshness, has an LLM judge whether it's a real warm signal.
Fuzzy-match badge companies to Salesforce accounts and enrich
Resolves messy hand-typed company names from badge scans to canonical Salesforce accounts using domain and fuzzy-name matching, enriches missing firmographics.
Daily rollup of scored webinar leads from Airtable into HubSpot lists
On a schedule, read newly scored webinar leads from Airtable, sync each into the matching HubSpot tiered list (Hot/Warm/Cold).
Instantly triage uploaded badge CSVs and notify the SDR lead
Accepts a badge-scan CSV via webhook, validates and dedupes it on the spot, checks each attendee against HubSpot.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.