AI AGENTS
Inbound demo prep from a HubSpot booking
When an inbound demo is booked through HubSpot, gathers company intel and lead context and posts a pre-demo brief to the sales rep's Slack so they qualify faster.
How it runs
The automated pipeline, trigger to output.
- TriggerInbound demo booked in HubSpotHubSpot
- ActionRead contact & company propertiesHubSpot
- LogicFlag fit by size & segment
- ActionResearch company & intentExa
- ActionDraft pre-demo brief with discovery questions
- OutputPost brief to assigned rep in SlackSlack
What it does
When a prospect books an inbound demo via HubSpot, the agent reads the lead and company record, researches the company's size, market, and recent activity, and assembles a short pre-demo brief: who they are, why they likely reached out, and questions worth asking. The brief reaches the assigned rep in Slack minutes after booking.
When to use it
You get inbound demo requests and reps need fast context to qualify and tailor the call. Ideal for PLG and inbound-heavy sales teams using HubSpot.
How it works
- 1A HubSpot meeting-booked event triggers the run.
- 2The agent reads the associated contact and company properties.
- 3It branches on whether the company looks like a fit by size and segment, flagging the brief accordingly.
- 4Exa researches the company for recent context and likely intent.
- 5The agent drafts a pre-demo brief with discovery questions.
- 6It posts the brief to the assigned rep in Slack.
Set it up
What you configure once, before turning it on.
- 1Connect HubSpotCRM, deals, marketing, support.
- 2Connect ExaNeural search across the web.
- 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 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.