AI AGENTS
SOC2 Policy Acknowledgment Audit Agent
Quarterly, reads your security-policy pages in Confluence, cross-checks who has acknowledged each one against your employee roster in Airtable.
How it runs
The automated pipeline, trigger to output.
- TriggerQuarterly schedule fires
- ActionFetch policy pages and revision datesConfluence
- ActionPull roster and acknowledgmentsAirtable
- LogicCompute per-employee unacknowledged policies
- ActionLog compliance snapshot as evidenceAirtable
- OutputDM overdue employees with policy linksSlack
What it does
Automates the SOC2 requirement that employees read and accept security policies (CC1.1, CC2.2). It reconciles the list of published policies in Confluence against acknowledgment records, surfaces who is overdue, and creates a defensible evidence trail of the chase.
When to use it
Use it every quarter, or after you publish a new or revised policy, so acknowledgment never silently lapses. Ideal for teams whose handbook and policies live in Confluence.
How it works
- 1A scheduled trigger fires each quarter.
- 2An agent fetches the current set of policy pages and their last-modified dates from Confluence.
- 3It pulls the active-employee roster and existing acknowledgments from Airtable.
- 4A logic step computes, per employee, which required policies are unacknowledged or were acknowledged before the latest revision.
- 5It writes the compliance snapshot back to Airtable as evidence.
- 6It sends each overdue employee a direct Slack reminder with links to the exact policies they still owe.
Set it up
What you configure once, before turning it on.
- 1Connect ConfluenceSpaces, pages, blueprints.
- 2Connect AirtableBases, tables, views, automations.
- 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.