OTHER
SOC2 Evidence Staleness Sweep (S3 artifacts → Confluence register)
On a weekly schedule, scans the SOC2 evidence bucket in S3, computes each artifact's age against its control's collection cadence.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires the evidence sweep
- ActionList evidence objects and last-modified dates in S3AWS S3
- LogicGroup by control, compute freshest-artifact age vs cadence
- ActionUpdate per-control freshness status in Confluence registerConfluence
- OutputPublish updated control register pageConfluence
What it does
Every week it walks your SOC2 evidence store in S3, reads the last-modified date of each control's artifact, and compares it to the freshness cadence you defined for that control (for example 30, 90, or 180 days). Controls whose newest artifact has aged past their window get flagged STALE in a Confluence control register so auditors and control owners always see current status.
When to use it
Use it when your evidence lives as files in S3 (screenshots, exported configs, signed PDFs) and your auditable source of truth is a Confluence page. It keeps the register honest between point-in-time audits without anyone manually checking file dates.
How it works
- 1A weekly schedule fires the sweep.
- 2It lists every object in the SOC2 evidence prefix in S3 and pulls each artifact's last-modified timestamp.
- 3Logic groups objects by control ID and computes the age of the freshest artifact per control, comparing it to that control's cadence.
- 4It writes the per-control freshness status (FRESH / DUE SOON / STALE) into the Confluence control register table.
- 5The updated register page is published as the run output.
Set it up
What you configure once, before turning it on.
- 1Connect AWS S3Buckets, objects, signed URLs.
- 2Connect ConfluenceSpaces, pages, blueprints.
- 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 Other workflows
Sweep stale visitor check-ins, auto-checkout, and flag overdue guests
On a recurring schedule this finds visitors still marked on-site past their expected departure, auto-checks-out anyone past end-of-day.
Pre-register a visitor, email a QR badge, and alert the host on arrival
When a host submits a visitor pre-registration form, this creates a visitor record, emails the guest a scannable QR badge with arrival instructions.
Build a daily expected-visitor roster and send it to the front desk
Every morning this pulls the day's pre-registered visitors from Airtable, builds a sorted arrival roster with hosts and times.
Agent-Driven Full IVR Re-Voicing for a Rebrand
An agent takes a rebrand brief from Notion, audits every IVR prompt for old naming, rewrites and re-synthesizes the affected ones with ElevenLabs, archives them to Dropbox.
Sync IVR Prompt Registry in Airtable to Fresh ElevenLabs Audio
Runs nightly against an Airtable IVR prompt registry, finds rows whose script text changed since last synthesis, regenerates only those ElevenLabs clips.
Slack-Approved IVR Re-Voicing After a Product Rename
On demand from Slack, drafts updated IVR prompt scripts for a renamed product, posts them for human approval.
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.