LEAD GENERATION
Detect repeat doc visitors and email account owners a daily warm-account digest
Aggregates documentation download history nightly, flags accounts whose visitors crossed a repeat-engagement threshold in the last week.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily morning schedule fires
- ActionQuery trailing-7-day download events from PostgresPostgres
- LogicFilter to accounts past repeat-engagement threshold
- LogicRank warming accounts and assign owner
- OutputEmail each owner a ranked warm-account digestGmail
- ActionRecord digest send timestamp in PostgresPostgres
What it does
Looks beyond single downloads to spot accounts that are quietly heating up. Each night it scans the rolling download log, counts distinct assets and visits per company over the trailing week, and surfaces the accounts crossing a repeat-engagement bar — then sends owners a ranked email so they prioritize the right outreach.
When to use it
Your buying signal is a pattern, not one click — a champion pulling multiple guides over several days. Ideal for PLG and developer-led motions where one download is noise but three in a week is a meeting.
How it works
- 1A scheduled trigger runs each morning before standup.
- 2Query the Postgres download-events table for the trailing 7 days, grouped by company.
- 3Filter to accounts past the repeat-visit threshold (distinct assets and total downloads).
- 4Rank the qualifying accounts by a weighted engagement score and attach the owning rep.
- 5Email each owner their personal ranked digest of warming accounts with last-touched assets.
- 6Stamp the digest send back to Postgres so the next run only re-flags genuinely new movement.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect GmailRead, draft, send, label.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Lead Generation workflows
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.
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.
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).
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.
Classify open-text webinar poll answers with AI and enrich the lead record
For webinars that use free-text poll questions, an AI step reads each attendee's written answers, classifies intent and pain points into structured fields.
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.