DEVOPS
Log every CVE scan to Postgres and report weekly staging-gate trends
Records each container image CVE scan result into a Postgres table as it happens.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook: completed scan resultHTTP webhook
- ActionUpsert scan record into Postgres historyPostgres
- LogicWeekly: aggregate block rate + recurring CVEs
- ActionRead Postgres and build trend digestPostgres
- OutputPost weekly trend report to TeamsMicrosoft Teams
What it does
Turns one-off scan results into a durable record and a weekly signal. Individual gate decisions are ephemeral; this captures them so you can see whether your block rate is rising, which CVEs keep reappearing, and which images repeatedly fail.
When to use it
Use it when you need evidence for security reviews or want to spot a base image that keeps dragging in the same vulnerabilities week after week.
How it works
- 1A webhook trigger fires once per completed scan with image, severities, CVE IDs, and the gate verdict.
- 2An action upserts the result into a Postgres scan-history table keyed by image digest and timestamp.
- 3A weekly schedule branch later reads the table and aggregates block rate, mean time-to-fix, and the most frequent recurring CVEs.
- 4An action formats the aggregates into a readable weekly digest.
- 5An output posts the trend report to Microsoft Teams for the platform and security teams.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect Microsoft TeamsChannels, chats, files.
- 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 DevOps workflows
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Open a Zoom war-room from a Datadog multi-alert storm
When a Datadog monitor crosses a critical threshold, this workflow dedupes against active incidents, and only for a genuinely new outage it creates a Zoom bridge.
Auto-spin a Zoom war-room when PagerDuty hits SEV-1
When a PagerDuty incident escalates to a critical severity, this workflow creates a dedicated Zoom meeting and posts the bridge link to the incident's Slack channel so responders…
Spin up a war-room on demand from a Slack slash command
When an engineer runs a Slack command, this workflow creates a Zoom bridge, opens a tracking Sentry-linked incident, files a Linear issue for follow-up.
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.