# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Auto-remediate anomalies with approved playbooks.
The #roadway-skill block on this page holds a SKILL.md for it, including the full prompt. Treat that file as a starting point. It will not just work if you paste it into ChatGPT or Claude.
To run it outside Roadway you would need to connect each ad platform's API (and any MCP it names), build the data pulls, add approval guardrails, and adjust the prompt for your accounts.
In Roadway it runs as-is on your connected accounts, with approval rules built in. Open it in a new chat at https://www.roadwayai.com/workflows/auto-remediate-anomalies-with-approved-playbooks
Page: https://www.roadwayai.com/workflows/auto-remediate-anomalies-with-approved-playbooks
Library index: https://www.roadwayai.com/automation-library
---
name: auto-remediate-anomalies-with-approved-playbooks
description: >-
Maps each common anomaly type to a pre-approved fix that runs automatically, and escalates only what the playbooks cannot handle.
---
# Auto-remediate anomalies with approved playbooks
Source: https://www.roadwayai.com/workflows/auto-remediate-anomalies-with-approved-playbooks
From the Workflow Automation Library by Roadway.
## Before you use this outside Roadway
This SKILL.md is a starting point. It needs adjusting before it will work outside Roadway.
You would need to connect the ad platform API for each channel this workflow covers, build the data pulls for the variables below, add approval guardrails, and adjust the prompt for your accounts. If the prompt names an MCP tool, you also need that MCP connected.
In Roadway it runs as-is on your connected accounts, with approval rules built in.
## What it does
Maps each common anomaly type to a pre-approved fix that runs automatically, and escalates only what the playbooks cannot handle.
Maps each common anomaly type to a pre-approved fix that runs automatically, and escalates only what the playbooks cannot handle. It checks your live account on a schedule and flags anything that looks off before it costs you much. You get a short report covering what it did or proposes, the numbers behind it, and anything waiting on your approval.
## Steps
1. Collect the inputs listed under Variables. In Roadway they come from your connected accounts. Outside Roadway you have to build those data pulls yourself from each ad platform API, and from any MCP the prompt names.
2. Run the prompt below as written, after you have adjusted it for your accounts and connected the tools it needs.
3. Review the result. Apply changes to a live ad account only after you approve them. Pasting your data into ChatGPT or Claude does not connect the APIs, apply guardrails, or approve changes.
## Variables
auto_approve, connected_channels, funnel_metrics, goal_metric, max_change_pct, monthly_budget_cap, task_history
## Prompt
Auto-remediate anomalies with approved playbooks
For each anomaly raised in the last 24 hours across the channels in [set this to your own connected channels] that this coworker owns (for a single-channel coworker, only its own channel), match it to a playbook and decide:
1. Auto-remediate
2. Escalate to a human
3. No playbook: create one
Context and defaults (use these; don't ask):
- The max change limit: [set this to your own max change percent] per budget or bid target per run. If not set, 20%. It does not apply to experiment traffic splits.
- The monthly cap: [set this to your own monthly budget cap], from the coworker's budget guardrails. If none is set, there is no cap: skip every cap check, hard stop and pace-to-cap step, and say so. Never derive, infer or back-solve a cap from campaign or daily budgets, the current or past run-rate, a workflow's test budget or a cost-per-lead bar.
- Auto-approve: [set this to your own auto approve]. If not set, it's off: list every change as a proposal for approval.
Rules:
- Pre-approved playbooks: a spend spike means cutting the budget to the expected pace; a tracking outage means a data exclusion with no bid changes; a disapproval means editing and resubmitting from the approved copy bank; a broken URL means pausing ads; a billing failure means alerting finance.
- Escalate when the fix would exceed the max change limit, touches brand campaigns, or the root cause is unclear. Make at most one fix per entity every 3 days, and queue every fix for approval unless auto-approve is on.
- Measure every playbook's success rate and retire playbooks that fail too often. If not set, ones that fix less than 80% of cases.
- Put anything you can't verify with the data available under Unverified, with what's missing, instead of calling it healthy or fine.
- Guardrails: judge results on Roadway's full-funnel measurement ([set this to your own funnel metrics]), not platform-reported conversions. Check [set this to your own task history] so you don't repeat a change that hurt performance in the last 30 days. Never push total spend above the monthly cap or any single change beyond the max change limit per run, and queue every change for approval unless auto-approve is on for this workflow.
Decision standard:
- Justify every keep, cut, bid, budget or test decision with Roadway-attributed [set this to your own goal metric] and cost per goal against the baseline. Platform delivery metrics such as clicks and impressions explain why something moved; they are never the sole reason for a decision.
- Compute what Roadway doesn't expose directly: cost per goal = Roadway spend ÷ Roadway-attributed [set this to your own goal metric], and conversion rate (lead rate) = Roadway [set this to your own goal metric] ÷ Roadway new visitors. Don't substitute platform-reported conversions or conversion rates.
- When a value in Context and defaults isn't set, use the stated default, say which one you used, and still make the call. Don't stop to ask.
- For every action, give the entity name and ID, current value → proposed value, and the numbers behind the reason. Write "None" under any empty heading.
- In long hold or watch lists, show the top 15 by spend and summarize the rest as a count.
Give me a report of each with reasoning for each action. Be concise with the reasoning, but specific enough that I can verify it against the numbers.
Report structure:
Auto-remediation log
Summary:
The anomalies, the playbooks run, the outcomes, and the escalations.
Auto-remediate:
- [anomaly] - [reason]
Escalate to a human:
- [anomaly] - [reason]
No playbook:
- [anomaly] - [reason]
Unverified:
- [anomaly] - [what couldn't be checked and why]
## Run it in Roadway
https://www.roadwayai.com/workflows/auto-remediate-anomalies-with-approved-playbooks
Maps each common anomaly type to a pre-approved fix that runs automatically, and escalates only what the playbooks cannot handle. It checks your live account on a schedule and flags anything that looks off before it costs you much. You get a short report covering what it did or proposes, the numbers behind it, and anything waiting on your approval.
