# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Enforce budget caps by product line or business unit.
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/enforce-budget-caps-by-product-line-or-business-unit
Page: https://www.roadwayai.com/workflows/enforce-budget-caps-by-product-line-or-business-unit
Library index: https://www.roadwayai.com/automation-library
---
name: enforce-budget-caps-by-product-line-or-business-unit
description: >-
Splits the monthly cap into product-line or business-unit sub-caps and enforces each one across channels.
---
# Enforce budget caps by product line or business unit
Source: https://www.roadwayai.com/workflows/enforce-budget-caps-by-product-line-or-business-unit
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
Splits the monthly cap into product-line or business-unit sub-caps and enforces each one across channels.
Splits the monthly cap into product-line or business-unit sub-caps and enforces each one across channels. It watches spend against the limits you set and shows you what it would change. 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, cost_guardrail, funnel_metrics, goal_metric, max_change_pct, monthly_budget_cap, naming_convention, slack_delivery, task_history
## Prompt
Enforce budget caps by product line or business unit
Map every campaign across the channels in [set this to your own connected channels] that this coworker owns (for a single-channel coworker, only its own channel) to a product line or business unit using the naming convention, sum spend against each sub-cap, and decide:
1. Within sub-cap
2. Slow down
3. Move budget between lines
4. Unmapped campaign
Context and defaults (use these; don't ask):
- The naming convention: [set this to your own naming convention]. If not set, infer the dominant pattern from existing names and say so.
- 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 delivery channel: [set this to your own slack delivery]. If Slack isn't connected, deliver in the run's thread.
- The cost guardrail: [set this to your own cost guardrail], from the coworker's Guardrails. If not set, 1.3x the baseline cost per goal. A workflow qualification bar (for example "cost per lead under $100 to build a page") is not a ceiling.
- 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:
- Sub-caps add up to the monthly cap. A line that overspends its sub-cap gets slowed down even if the total is fine.
- Move budget between lines only with owner approval in the delivery channel, and only from a line with no efficient spend left to one with budget-limited campaigns under the cost guardrail.
- Unmapped campaigns break the cap logic, so flag and rename them right away.
- 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.
- Delivery-constrained (budget-limited) means it spent nearly all of its daily budget on most recent days and, on search, lost impression share to budget. If not set, 95%+ of the daily budget on 4+ of the last 7 days, and 10%+ impression share lost to budget.
- 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:
Product-line budget cap report
Summary:
Spend vs sub-cap per line and channel, and the moves made.
Within sub-cap:
- [product line] - [reason]
Slow down:
- [product line] - [reason]
Move budget between lines:
- [product line] - [reason]
Unmapped campaign:
- [product line] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/enforce-budget-caps-by-product-line-or-business-unit
Splits the monthly cap into product-line or business-unit sub-caps and enforces each one across channels. It watches spend against the limits you set and shows you what it would change. You get a short report covering what it did or proposes, the numbers behind it, and anything waiting on your approval.
