DEVOPS
Auto-promote a passing Vercel preview and notify Slack on GitLab MR approval
When a GitLab MR is approved and its Vercel preview clears both a Lighthouse and an accessibility re-check, the workflow promotes the deployment to staging via Vercel and posts…
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab MR approvedGitLab
- ActionRe-run Lighthouse + axe-core on previewShell
- LogicPass or fail from combined results
- ActionPromote deployment to staging on passVercel
- OutputNotify Slack with scores or block reasonSlack
What it does
Closes the loop on the QA gate: on approval it re-verifies the preview is still healthy, then promotes it to the staging environment automatically and announces the result. A failing re-check blocks promotion and explains the failure rather than shipping silently.
When to use it
Use it when approval should mean "ship to staging now" but you refuse to promote anything that has drifted out of spec since the last audit. Ideal for teams wanting hands-off promotion with a final safety check.
How it works
- 1A GitLab MR-approved webhook fires with the preview deployment reference.
- 2A shell step re-runs Lighthouse and an axe-core a11y check against the preview URL.
- 3A logic branch decides pass or fail from the combined results.
- 4On pass, a Vercel action promotes the deployment to the staging environment.
- 5On pass, a Slack message posts the scores and the live staging URL.
- 6On fail, promotion is skipped and Slack receives the blocking reason instead.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect ShellRun sandboxed commands inside the workspace.
- 3Connect VercelDeploys, runtime logs, analytics.
- 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.