AI AGENTS
Post-Event Hot-Lead Routing Digest
On a nightly schedule during the show, scores the day's captured leads, assigns each to the right rep by territory, and sends a ranked follow-up digest to Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule after floor close
- ActionPull the day's captured leadsAttio
- LogicScore and rank leads by fit and recency
- LogicAssign owner by territory rule
- ActionWrite owner and priority back to CRMAttio
- OutputSend per-rep ranked digestSlack
What it does
Runs at the end of each show day, pulls every lead captured since the last run, scores them on engagement and fit, assigns each to an owning rep by territory, and delivers a ranked digest so the team knows exactly who to call first tomorrow morning.
When to use it
Use it for multi-day conferences where leads pile up fast and you want disciplined next-day follow-up instead of a chaotic spreadsheet. Best when reps own territories or product lines you can map cleanly.
How it works
- 1A nightly schedule fires after the floor closes.
- 2The workflow queries the CRM for leads created or touched that day.
- 3A scoring step ranks each lead by demo interest, company size, and recency.
- 4A routing branch assigns each lead to a rep based on territory rules.
- 5Owner and priority tier are written back to Attio.
- 6A per-rep ranked digest is posted to Slack with the top contacts and suggested next action.
Set it up
What you configure once, before turning it on.
- 1Connect AttioReal-time CRM with structured data + powerful views.
- 2Connect SlackChannels, DMs, threads, mentions.
- 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 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.