ENGINEERING
Vercel preview failure triage to a Linear issue
When a Vercel preview smoke check fails, an AI step reads the failing responses and recent commit diff, writes a likely-cause triage summary.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel preview deployment readyVercel
- ActionRun smoke request against previewHTTP webhook
- LogicContinue only if smoke check failed
- ActionFetch PR diff and commits from GitHubGitHub
- ActionDraft likely-cause triage with AIOpenAI
- OutputFile assigned Linear issue with triageLinear
What it does
This workflow watches Vercel preview smoke results and, when one fails, gathers the failing route output and the PR's changed files, asks an AI step to summarize the most probable cause, and opens a Linear issue with that triage attached — assigned to the PR author and linked back to the deploy.
When to use it
Use it when preview failures otherwise vanish into a Slack channel and never get tracked. This turns every failed preview into an actionable, owned ticket with a head start on root cause.
How it works
- 1A Vercel preview-ready webhook triggers a smoke request against the preview.
- 2A logic step proceeds only when the smoke check fails.
- 3The flow fetches the changed files and commit messages from GitHub for the PR.
- 4An OpenAI step analyzes the failure plus the diff and drafts a likely-cause triage note.
- 5A Linear issue is created with the triage, the preview URL, and the PR link, assigned to the author.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect HTTP webhookTrigger any URL on agent actions.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 4Connect OpenAIModels, embeddings, files.
- 5Connect LinearIssues, projects, cycles, triage.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Engineering workflows
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Block PRs that add incompatible Hugging Face model licenses
When a pull request adds or bumps a Hugging Face model dependency, it fetches the model card license, checks it against your org's allowed-license policy.
Quarterly Logging Hygiene Audit Agent
An agent-driven quarterly sweep that surveys all Axiom datasets, builds a logging-hygiene scorecard per service.
Post-Merge Log Volume Recheck After Downsampling PR
After a log-level PR merges, waits a day then re-queries Axiom to confirm the targeted stream's volume actually dropped.
Axiom Ingest Cost Spike to Linear Triage Ticket
When Axiom ingest volume spikes beyond its baseline, identifies which service caused it and files a Linear ticket with the offending log stream, sample lines, and a downsampling…
File a Linear license-review ticket for risky model adds
When a PR introduces a Hugging Face model with a non-permissive or unknown license, it opens a Linear issue assigned to the legal-review team with the model, license.
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.