DEVOPS
Nightly Vercel env drift scan logged to Axiom with Slack digest
On a nightly schedule, audit every Vercel project's environment variables against its GitLab manifest, write each drift event to Axiom for trend analysis.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule
- ActionList Vercel projects and fetch each env configVercel
- ActionRead per-project manifest from GitLabGitLab
- LogicDiff each project, collect drift findings
- ActionEmit drift events to AxiomAxiom
- OutputPost consolidated digest to SlackSlack
What it does
This is the scheduled, fleet-wide version of env auditing. Every night it walks all your Vercel projects, compares each one's environment config to its committed manifest in GitLab, records every discrepancy as a structured event in Axiom, and delivers a single morning digest to Slack. Over time Axiom becomes your drift history — you can chart which projects drift most and when.
When to use it
Use it when you run many Vercel projects and want a daily health check rather than a per-deploy gate. Good for platform teams that need an audit trail and want to spot slow, creeping config rot before it causes an incident.
How it works
- 1A nightly schedule triggers the scan.
- 2The flow lists all Vercel projects and pulls each project's environment variables.
- 3For each project it reads the matching manifest from GitLab and diffs the two.
- 4Every drift finding is emitted to Axiom as a structured event tagged by project and severity.
- 5A summary step rolls all findings into one digest.
- 6The digest is posted to Slack so the team starts the day with the full picture.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect GitLabRepos, MRs, pipelines, registry.
- 3Connect AxiomLog streams, queries, dashboards.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.