# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Fund signal-based surges within the budget cap.
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/fund-signal-based-surges-within-the-budget-cap
Page: https://www.roadwayai.com/workflows/fund-signal-based-surges-within-the-budget-cap
Library index: https://www.roadwayai.com/automation-library
---
name: fund-signal-based-surges-within-the-budget-cap
description: >-
When signal-based workflows surge spend (competitor outages, trends, launches), funds the surge by cutting the least efficient spend elsewhere so the cap holds.
---
# Fund signal-based surges within the budget cap
Source: https://www.roadwayai.com/workflows/fund-signal-based-surges-within-the-budget-cap
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
When signal-based workflows surge spend (competitor outages, trends, launches), funds the surge by cutting the least efficient spend elsewhere so the cap holds.
When signal-based workflows surge spend (competitor outages, trends, launches), funds the surge by cutting the least efficient spend elsewhere so the cap holds. It watches spend against the limits you set and shows you what it would change. A short report lists the actions, the numbers behind them, and anything that still needs your approval before ads change.
## 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, experiment_budget_pct, funnel_metrics, goal_metric, max_change_pct, monthly_budget_cap, task_history
## Prompt
Fund signal-based surges within the budget cap
For each active surge from signal-based workflows, find funding inside the monthly cap and decide:
1. Fund from lowest-efficiency campaigns
2. Fund from experiment budget
3. Reject surge
Context and defaults (use these; don't ask):
- 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.
- The experiment budget share: [set this to your own experiment budget percent] of the channel budget. If not set, 10%.
- 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.
- Auto-approve: [set this to your own auto approve]. If not set, it's off: list every change as a proposal for approval.
Rules:
- Fund from campaigns with the worst cost of the next goal across all channels first, never from brand protection or campaigns in learning.
- Fund from experiment budget (the experiment budget share) when the surge is itself a test.
- Reject the surge when funding it would push any campaign below its minimum viable budget, or the surge lacks a clear signal.
- If no campaign qualifies to receive budget, still make the justified cuts and report the freed budget as unallocated savings for approval. Never pause the entity producing the most [set this to your own goal metric] at or below baseline.
- 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:
Surge funding report
Summary:
The surges funded, where the money came from, and the cap status.
Fund from lowest-efficiency campaigns:
- [surge] - [reason]
Fund from experiment budget:
- [surge] - [reason]
Reject surge:
- [surge] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/fund-signal-based-surges-within-the-budget-cap
When signal-based workflows surge spend (competitor outages, trends, launches), funds the surge by cutting the least efficient spend elsewhere so the cap holds.
When signal-based workflows surge spend (competitor outages, trends, launches), funds the surge by cutting the least efficient spend elsewhere so the cap holds. It watches spend against the limits you set and shows you what it would change. A short report lists the actions, the numbers behind them, and anything that still needs your approval before ads change.
