AI AGENTS
Inbound Lead Research Dossier in HubSpot
When a new lead is created in HubSpot, an agent researches the person and their company across the web, writes a sourced pre-call dossier.
How it runs
The automated pipeline, trigger to output.
- TriggerNew contact created in HubSpotHubSpot
- ActionResearch person and company on the web (Exa)Exa
- ActionScrape company site with FirecrawlFirecrawl
- LogicCheck signal sufficiency; flag thin leads
- ActionWrite sourced pre-call dossier (OpenAI)OpenAI
- OutputSave dossier to HubSpot contact notesHubSpot
What it does
Gives sales reps an instant, cited dossier on every inbound lead. The moment a contact is created in HubSpot, the agent researches the person, their company, recent news, and likely pain points, then writes a tight pre-call brief with sources and attaches it to the record.
When to use it
When reps waste time manually Googling each lead before a call, or show up underprepared. This front-loads the research so the first conversation is informed.
How it works
- 1A new contact created in HubSpot triggers the flow.
- 2The agent searches the web with Exa for the person and their company, including recent news and funding.
- 3Firecrawl scrapes the company's site for positioning and product details.
- 4A logic step confirms enough signal was found; thin leads are flagged for light-touch follow-up instead.
- 5OpenAI writes a sourced dossier: company snapshot, likely needs, and three suggested talking points.
- 6The dossier is written back to the HubSpot contact's notes.
Set it up
What you configure once, before turning it on.
- 1Connect HubSpotCRM, deals, marketing, support.
- 2Connect ExaNeural search across the web.
- 3Connect FirecrawlCrawl, scrape, structured extract.
- 4Connect OpenAIModels, embeddings, files.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More AI Agents workflows
Stale Doc-PR Chaser for Runbook Gaps
On a daily schedule the agent finds runbook doc PRs that were opened from resolved incidents but never reviewed, summarizes what each one fixes.
On-Call Runbook Gap Closer: Resolved Sentry Issues to Doc PRs
An agent reads each newly resolved Sentry issue, compares the actual fix against your existing runbook, and opens a GitHub PR adding the missing remediation steps.
Datadog Bill Spike Attribution Agent
When a daily Datadog cost check detects a spend jump, an agent attributes the increase to the specific services and metric types driving it and posts a ranked breakdown to Slack.
Sentry-to-Confluence Runbook Updater
When a Sentry issue is resolved, the agent finds the matching Confluence runbook page and proposes an inline update with the verified fix.
Custom Metrics Cardinality Spike Pager
A webhook from a Datadog monitor fires when custom-metric cardinality jumps; an agent pinpoints the offending metric and tag, estimates the added cost.
Resolved Incident to Public Troubleshooting Doc
For customer-facing errors resolved in Sentry, the agent drafts a sanitized troubleshooting entry and opens a PR to your ReadMe documentation.
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.