AI AGENTS
Summarize daily prompt-moderation verdicts into a report
Runs on a schedule to roll up the previous day's prompt-moderation log from Postgres, computes block rates and top violation categories, and delivers a digest to your team.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionQuery last 24h of verdicts from PostgresPostgres
- LogicAggregate block rate, categories, offenders
- ActionDraft narrative summary from aggregatesOpenAI
- OutputPost moderation digest to SlackSlack
What it does
This workflow turns your moderation audit log into a daily operations report. It reads the prior 24 hours of verdicts from Postgres, aggregates how many prompts were allowed versus blocked, breaks blocks down by policy category and repeat offenders, and sends a readable summary to your team channel.
When to use it
Use it when you already have a moderation gate writing verdicts to Postgres and now need visibility into how it is performing: spotting abuse spikes, tuning thresholds, and reporting safety metrics to stakeholders.
How it works
- 1A daily schedule triggers the run.
- 2A Postgres query pulls all verdict rows from the last 24 hours.
- 3A logic step aggregates totals, block rate, top categories, and top offending users.
- 4An OpenAI step drafts a concise narrative summary from the aggregates.
- 5The formatted digest is posted to a Slack channel for the trust-and-safety team.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect OpenAIModels, embeddings, files.
- 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
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.