DEVOPS
Gate the GitLab merge request on a Vercel preview smoke run
On a GitLab merge request event, waits for the matching Vercel preview, runs smoke checks, and posts a commit status plus an MR note so the pipeline can require a green preview.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab merge request opened or updatedGitLab
- ActionResolve and await Vercel previewVercel
- ActionSmoke-test preview endpointsHTTP webhook
- LogicClassify healthy vs broken
- OutputPost GitLab status and MR noteGitLab
What it does
Bridges GitLab merge requests and Vercel previews. When an MR is opened or updated, the workflow resolves the Vercel preview deployment for that branch, smoke-tests the ephemeral environment, and writes the result back to GitLab as a commit status and a threaded MR note. GitLab pipeline rules can then refuse to merge until the preview is verified.
When to use it
Use it when your repo lives in GitLab but your frontend deploys through Vercel, and you want the same running-environment gate GitHub users get. Ideal for teams that treat the preview as the source of truth for review.
How it works
- 1A GitLab merge request hook fires on open or push.
- 2A Vercel action looks up the preview deployment tied to the MR's source branch and waits for ready.
- 3An HTTP step exercises the preview's key paths and captures the results.
- 4A logic branch classifies the run as healthy or broken.
- 5A GitLab action posts the commit status and an MR note with the smoke summary and failing endpoints.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect VercelDeploys, runtime logs, analytics.
- 3Connect HTTP webhookTrigger any URL on agent actions.
- 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.