DEVOPS
Run Datadog synthetics against the preview and gate on results
Triggers a Datadog synthetic test batch against the new Vercel preview URL, waits for outcomes, and blocks merge via a GitHub status when any synthetic check fails.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel preview deployment readyVercel
- ActionTrigger Datadog synthetic batch on preview URLDatadog
- ActionAwait batch and fetch resultsDatadog
- LogicRequire all synthetics green
- OutputSet GitHub merge gate statusGitHub
What it does
Uses your existing Datadog synthetic tests as the smoke gate for ephemeral previews. When a Vercel preview is ready, it kicks off a tagged Datadog synthetic batch pointed at the preview URL, polls until the batch finishes, and turns the aggregate outcome into a GitHub commit status. Real browser and API checks decide whether the PR can merge.
When to use it
Use it when you've already invested in Datadog synthetics for production and want to reuse those exact journeys on previews — getting browser-level coverage instead of hand-rolled HTTP pings, with results visible in the same Datadog dashboards.
How it works
- 1Vercel signals that the preview deployment is ready.
- 2A Datadog action triggers the synthetic test batch with the preview URL injected as a variable.
- 3The workflow waits for the batch to complete and pulls per-test results.
- 4A logic branch passes only if every synthetic check is green.
- 5A GitHub commit status is written to gate the merge, carrying a link to the Datadog batch run.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect DatadogMetrics, traces, log search.
- 3Connect GitHubRepos, issues, pull requests, 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
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.