AI AGENTS
Usage-drop trigger that launches a retention play
When an account's product usage drops sharply, an agent confirms the decline, picks the right retention play.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook fires on a usage-drop eventHTTP webhook
- ActionFetch billing tier and renewal status from StripeStripe
- LogicConfirm drop vs. baseline; exit on false alarms
- LogicSelect the matching retention play
- ActionFlag risk and log the play on the HubSpot dealHubSpot
- OutputAlert the account owner in Slack with draft outreachSlack
What it does
Listens for a usage-drop event from your product analytics (sent via webhook), confirms the decline is real against historical baselines, and selects a retention play matched to why usage fell. It then drafts a re-engagement offer or check-in and notifies the account owner before the drop hardens into churn.
When to use it
Use it when leading-indicator churn shows up in usage long before the renewal date. Ideal for product-led teams who want to catch silent disengagement the moment it happens rather than at quarterly review.
How it works
- 1A webhook from your analytics tool fires when an account crosses a usage-drop threshold.
- 2The agent pulls the account's billing tier and renewal status from Stripe to size the response.
- 3It compares current vs. baseline usage to rule out false alarms; non-material drops exit early.
- 4Based on the signal it selects a play: feature enablement, onboarding nudge, or commercial save offer.
- 5It drafts the outreach and updates the HubSpot deal with the risk flag and recommended play.
- 6The account owner is alerted in Slack with the draft ready to send.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect StripeCustomers, subscriptions, payments.
- 3Connect HubSpotCRM, deals, marketing, support.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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
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.
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.
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.
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.
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.
Weekly On-Call Doc-Gap Digest
Each week the agent reviews every Sentry issue resolved in the last 7 days, ranks the ones whose runbook coverage is missing or thin.
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.
