AI AGENTS
Stale Vendor Document Chaser
Runs daily to find vendors stuck mid-onboarding with missing W-9s or unverified bank details, sends escalating reminder emails.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionQuery Notion for incomplete vendor recordsNotion
- LogicBucket vendors by days stalled (3 / 7 / 14+)
- ActionSend urgency-tuned reminder emailGmail
- OutputEscalate 14+ day stalls to operations SlackSlack
What it does
Keeps onboarding moving by finding vendors whose paperwork has gone quiet. Each day it scans for incomplete records, sends a reminder tuned to how long they've stalled, and escalates the truly stuck ones to a human owner.
When to use it
When vendors routinely drop off after starting onboarding and nobody owns the follow-up, leaving payable setups half-finished for weeks.
How it works
- 1A daily schedule triggers the run.
- 2The flow queries the vendor Notion database for records missing a W-9 or with unverified bank details.
- 3A logic branch buckets each vendor by days stalled: 3, 7, or 14+.
- 4Gmail sends a reminder whose tone and urgency match the bucket.
- 5Vendors stalled 14+ days are posted to the operations Slack channel tagged to an owner for manual outreach.
Set it up
What you configure once, before turning it on.
- 1Connect NotionPages, databases, comments.
- 2Connect GmailRead, draft, send, label.
- 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
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.