DEVOPS
On-demand parity check between Vercel preview and production env config
Triggered manually before a release, compare the environment variables of a Vercel preview deployment against production, flag every key that differs or is missing.
How it runs
The automated pipeline, trigger to output.
- TriggerManual run with target preview deployment
- ActionFetch preview env config from VercelVercel
- ActionFetch production env config from VercelVercel
- ActionRead environment-aware manifest from GitLabGitLab
- LogicDiff preview vs prod, build go/no-go report
- OutputPost parity report to SlackSlack
What it does
This workflow answers one release-day question: does my preview environment actually match production? Run it on demand against a specific preview deployment and it pulls both the preview and production env configs from Vercel, diffs them key by key, and tells you exactly which variables differ, which are missing on either side, and whether the preview is safe to promote. It cross-checks against the GitLab manifest so it can tell intentional differences from accidental ones.
When to use it
Use it right before promoting a preview to production, or when a feature works in preview but you suspect a config mismatch will break it in prod. It is the pre-flight checklist for env parity.
How it works
- 1An operator triggers the run, supplying the preview deployment to check.
- 2The flow fetches the preview deployment's env config from Vercel.
- 3It fetches the current production env config from Vercel.
- 4It reads the GitLab manifest to know which keys are expected to differ by environment.
- 5A diff step produces a parity report and a go/no-go verdict.
- 6The report is posted to Slack for the release owner to approve.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect GitLabRepos, MRs, pipelines, registry.
- 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 DevOps workflows
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.
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…
Page on-call when a Hugging Face Space build is stuck or errored
Polls Hugging Face Space runtime status on a schedule and opens a PagerDuty incident when a Space sits in a build or error state past a deadline, with a Slack heads-up.
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.
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.
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.