AI AGENTS
Trust-Center Source Freshness Audit Before Drafting
On a schedule, checks that the Confluence trust-center pages cited by recent questionnaire answers are still current.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly freshness audit schedule
- ActionPull most-cited Confluence pages from draftsPostgres
- ActionFetch page metadata and review labelsConfluence
- ActionClassify pages as current, stale, or changed
- LogicFilter to pages failing freshness policy
- OutputSend Slack digest of flagged pages with ownersSlack
What it does
Guards against answering questionnaires from outdated evidence. It scans the Confluence pages most frequently cited in questionnaire drafts, checks last-modified dates and approval status, and surfaces controls that are stale or were just edited and may need re-review.
When to use it
Run it weekly if your trust center evolves and you worry about shipping answers backed by a year-old SOC 2 page or an unreviewed edit. It keeps the knowledge base trustworthy without manual audits.
How it works
- 1A weekly schedule triggers the audit.
- 2The workflow pulls the list of most-cited Confluence pages from recent drafts.
- 3It fetches each page's metadata: last-modified date, owner, and review label.
- 4The agent classifies each page as current, stale, or recently-changed-needs-review.
- 5A logic step filters to only pages that fail the freshness policy.
- 6A Slack digest lists the flagged pages with owners so they can be refreshed before the next questionnaire.
Set it up
What you configure once, before turning it on.
- 1Connect ConfluenceSpaces, pages, blueprints.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 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.