CHATBOTS
Stale Ownership Detector with Slack Confirm Nudge
Finds catalog entries whose ownership hasn't been confirmed recently and DMs the listed owner in Slack to confirm or reassign, updating the catalog from their reply.
How it runs
The automated pipeline, trigger to output.
- TriggerMonthly schedule fires
- ActionQuery catalog for entries past the confirmation freshness windowPostgres
- LogicGroup stale services by their current listed owner
- ActionDM each owner in Slack with Confirm / Reassign buttonsSlack
- ActionUpdate last_confirmed or owner in Postgres from the replyPostgres
- OutputPost a digest of unresponsive owners to the platform channelSlack
What it does
Fights ownership rot. On a schedule it scans the service catalog for entries that haven't been confirmed past a freshness window, then DMs each listed owner in Slack with a confirm-or-reassign prompt. Their button reply updates the catalog directly, so ownership data decays gracefully instead of silently going wrong.
When to use it
When teams reorg, people leave, and your catalog quietly points incidents at the wrong person. Run it monthly to keep the data trustworthy without a manual audit.
How it works
- 1A monthly schedule fires.
- 2It queries Postgres for catalog rows where `last_confirmed` is older than the freshness threshold.
- 3A logic step groups stale services by current listed owner.
- 4It DMs each owner in Slack with their stale services and Confirm / Reassign buttons.
- 5On a Confirm reply it stamps `last_confirmed`; on Reassign it updates the owner field in Postgres.
- 6It posts a digest of unresponsive owners to the platform channel for follow-up.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 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 Chatbots workflows
Discord Onboarding Completion to CRM Sync
The moment a member finishes Discord onboarding, captures their submitted profile answers, creates or updates a contact in HubSpot.
Discord FAQ-Gated Role Concierge
Greets each new Discord member in a private onboarding thread, walks them through required FAQ steps one at a time.
Discord FAQ Free-Text Answer Grader
When a member submits a free-text answer in their onboarding thread, an agent grades it against the canonical FAQ knowledge base, replies with targeted feedback.
Discord verify-button onboarding via web form webhook
Receives a completed external verification form by webhook, matches it to the Discord account, grants the verified role, and confirms back to the member in Discord.
Discord intro-gated role granting concierge
Watches your #introductions channel, uses AI to confirm a new member's intro is genuine and complete, then auto-assigns the verified Member role and welcomes them.
Daily Discord Digest of Repeated WAF False-Positive Reports
Each morning, scans logged Discord WAF reports in Postgres, groups them by the Cloudflare rule that keeps firing.
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.