DEVOPS
Auto-open a GitLab MR to reconcile the env manifest after dashboard edits
When a Vercel env var changes outside of code, detect the drift against the GitLab manifest and automatically open a merge request that updates the manifest to match.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel env var updated webhookVercel
- ActionFetch current project env config from VercelVercel
- ActionRead existing manifest from GitLabGitLab
- LogicDiff and decide if manifest is stale
- ActionCommit updated manifest and open GitLab MRGitLab
- OutputPost MR link to SlackSlack
What it does
Instead of just flagging drift, this workflow closes the loop. When someone edits an environment variable in the Vercel dashboard, it detects the difference from the committed manifest and opens a GitLab merge request that updates the manifest to reflect the live value. A human still reviews and merges — but the tedious work of capturing the change as code is done for them.
When to use it
Use it when emergency dashboard edits are a fact of life and your problem isn't preventing them but recording them. It keeps your `env.manifest.json` honest without forcing every hotfix through a PR first.
How it works
- 1A Vercel env-var-updated webhook fires.
- 2The flow fetches the current full env config for the affected project from Vercel.
- 3It reads the existing manifest from GitLab and diffs the two.
- 4If the manifest is out of date, it generates an updated manifest file.
- 5It commits the change to a new branch and opens a merge request in GitLab with the diff in the description.
- 6The MR link is posted to Slack tagging the engineer who made the edit.
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
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.