DEVOPS
Crawl Vercel preview for broken links and a11y violations before promote
Crawls a Vercel preview deployment for broken internal links and accessibility violations, and blocks promotion to production while filing a Linear ticket for each defect found.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel preview deployment readyVercel
- ActionCrawl preview for broken linksFirecrawl
- ActionRun accessibility scan on pagesShell
- LogicAny broken links or a11y violations?
- OutputFile Linear ticket per defectLinear
What it does
This workflow does a content-integrity sweep of each preview before it can ship. It crawls the preview site, following internal links to find 4xx/5xx pages, and runs an automated accessibility scan on each page. If it finds broken links or serious a11y violations it keeps the deployment unpromoted and opens a tracked defect for each issue so nothing gets lost.
When to use it
Use it on marketing or docs sites where dead links and accessibility regressions are common and you want them caught and ticketed automatically rather than discovered by users.
How it works
- 1A Vercel preview-ready webhook provides the preview URL and deployment ID.
- 2A Firecrawl step crawls the preview site and returns the link graph with HTTP status codes per page.
- 3A shell step runs an axe-core accessibility scan on the crawled pages and emits violations.
- 4A logic branch checks whether any broken links or critical a11y violations exist.
- 5If clean, an action promotes the deployment on Vercel. If not, it stays unpromoted and a Linear issue is created per defect with the page URL and details.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect FirecrawlCrawl, scrape, structured extract.
- 3Connect ShellRun sandboxed commands inside the workspace.
- 4Connect LinearIssues, projects, cycles, triage.
- 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.