AI AGENTS
Renewal Deadline Escalation Monitor
On a daily schedule, an agent scans contracts for approaching auto-renew and notice-period deadlines.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule
- ActionRead renewal and notice dates from NotionNotion
- LogicFind at-risk, unprepared renewals
- ActionAgent builds escalation summary
- OutputPost escalation to Slack with owner tagSlack
What it does
This workflow makes sure no renewal slips into auto-renew unnoticed. Each day the agent scans your contract records for upcoming auto-renew dates and notice-period cutoffs, checks whether prep work has actually been done, and escalates the renewals that are running out of runway without a brief, an owner, or a decision logged.
When to use it
Use it as a safety net on top of your renewal pipeline, especially when notice periods are strict and an unworked renewal means another year locked in at current pricing. Ideal for ops teams managing many overlapping contract calendars.
How it works
- 1A daily schedule starts the deadline sweep.
- 2The agent reads all contracts and their renewal and notice-period dates from Notion.
- 3A logic step finds contracts inside the danger window and checks for a completed brief and assigned owner.
- 4Contracts that are at-risk and unprepared are separated from those on track.
- 5The agent posts an escalation to Slack tagging the owner, with days remaining and what's missing.
Set it up
What you configure once, before turning it on.
- 1Connect NotionPages, databases, comments.
- 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
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.