DEVOPS
Vercel Build Slowdown to Honeycomb Trace Correlation
On a slow Vercel build, queries Honeycomb build traces to find which step (install, compile, bundle) regressed and posts the culprit phase with timing deltas to Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel deployment succeeded webhookVercel
- LogicCheck if build duration exceeds threshold
- ActionQuery Honeycomb for per-phase span durationsHoneycomb
- LogicDiff phases vs baseline; pick largest regression
- OutputPost culprit phase + trace link to SlackSlack
What it does
When a Vercel build runs long, this workflow doesn't just say "build is slow" — it queries your Honeycomb build instrumentation to pinpoint which phase regressed: dependency install, type-check, compilation, or asset bundling. It then sends a Slack message naming the culprit phase with before/after timing deltas.
When to use it
Use it when your builds are instrumented with Honeycomb spans and you want phase-level attribution instead of a single opaque duration number. Best for teams debugging whether a slowdown came from a new dependency, a heavier transpile step, or bundling bloat.
How it works
- 1A Vercel deployment-succeeded webhook delivers the build ID and duration.
- 2A logic step checks whether duration exceeds the alert threshold.
- 3If slow, the workflow queries Honeycomb for the build's per-phase span durations and the trailing average per phase.
- 4It diffs each phase against its baseline to find the largest regression.
- 5It posts the offending phase, its delta, and a Honeycomb trace link to the engineering Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect HoneycombDistributed traces and queries.
- 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.