# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Update partner keywords and copy when a partner renames or retires a product.
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/update-partner-keywords-and-copy-when-a-partner-renames-or-retires-a-product
Page: https://www.roadwayai.com/workflows/update-partner-keywords-and-copy-when-a-partner-renames-or-retires-a-product
Library index: https://www.roadwayai.com/automation-library
---
name: update-partner-keywords-and-copy-when-a-partner-renames-or-retires-a-product
description: >-
When a partner renames, rebrands or retires a product you integrate with, finds every keyword, headline, sitelink and context hint that uses the old name, adds the new name, and pauses ads for an integration that will stop working.
---
# Update partner keywords and copy when a partner renames or retires a product
Source: https://www.roadwayai.com/workflows/update-partner-keywords-and-copy-when-a-partner-renames-or-retires-a-product
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 a partner renames, rebrands or retires a product you integrate with, finds every keyword, headline, sitelink and context hint that uses the old name, adds the new name, and pauses ads for an integration that will stop working.
Each run, it reads your partners' blogs, changelogs and docs. When a partner renames, rebrands or retires a product you integrate with, it finds every keyword, headline, sitelink and context hint that uses the old name, adds the new name, and pauses ads for an integration that will stop working. It checks for its trigger on every scheduled run, so you can act on it then instead of waiting for your next review. 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
approved_claims, auto_approve, funnel_metrics, goal_metric, max_change_pct, monthly_budget_cap, partners, task_history, top_landing_pages
## Prompt
Update partner keywords and copy when a partner renames or retires a product
Check the blogs, changelogs and docs of each partner in [set this to your own partners] for a product rename, rebrand or end-of-life notice not seen on the last run, and for every keyword, headline, sitelink and context hint that uses the affected name, decide:
1. Add the new name
2. Rewrite copy
3. Pause retired integration ads
4. No change needed
Context and defaults (use these; don't ask):
- Partners: [set this to your own partners]. If it isn't available, say so and stop.
- Web search: read partner blogs, changelogs and docs with the web search tool. Changelogs can also come from a Notion, Linear or GitHub MCP if one is connected. If a source can't be read, say which one.
- The approved claims: [set this to your own approved claims]. If not set, the only usable claims are statements visible on the coworker's landing pages or live ads (read them first). Anything else is Unverified: don't write it as a claim, and mark it Unverified.
- The top landing pages: [set this to your own top landing pages]. If not set, rank pages by Roadway lead rate ([set this to your own goal metric] ÷ new visitors) for the same intent since the last run.
- 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 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:
- Only act on renames and retirements confirmed on the partner's own blog, changelog or docs. Skip rumors.
- Add the new name: add the new product name as exact and phrase match keywords next to the old ones, and keep the old name while it still gets searches.
- Rewrite copy: change headlines, descriptions, sitelinks and ChatGPT context hints to the new name, keeping character limits and pinning.
- Pause retired integration ads: pause ads and ad groups that promote an integration that will stop working, on or before the end date in the notice, and point sitelinks to the replacement integration page if one exists.
- Check the partner's brand rules before using the new name or logo.
- 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 already hurt performance. 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:
Partner rename and retirement report
Summary:
The renames and retirements found, and every keyword, ad and asset changed or paused.
Add the new name:
- [keyword, ad or asset] - [reason]
Rewrite copy:
- [keyword, ad or asset] - [reason]
Pause retired integration ads:
- [keyword, ad or asset] - [reason]
No change needed:
- [keyword, ad or asset] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/update-partner-keywords-and-copy-when-a-partner-renames-or-retires-a-product
Update partner keywords and copy when a partner renames or retires a product
Update partner keywords and copy when a partner renames or retires a product
When a partner renames, rebrands or retires a product you integrate with, finds every keyword, headline, sitelink and context hint that uses the old name, adds the new name, and pauses ads for an integration that will stop working.
Each run, it reads your partners' blogs, changelogs and docs. When a partner renames, rebrands or retires a product you integrate with, it finds every keyword, headline, sitelink and context hint that uses the old name, adds the new name, and pauses ads for an integration that will stop working. It checks for its trigger on every scheduled run, so you can act on it then instead of waiting for your next review. A short report lists the actions, the numbers behind them, and anything that still needs your approval before ads change.