# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Launch campaigns from product changelog releases for X Ads.
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/launch-campaigns-from-product-changelog-releases-for-x-ads
Page: https://www.roadwayai.com/workflows/launch-campaigns-from-product-changelog-releases-for-x-ads
Library index: https://www.roadwayai.com/automation-library
---
name: launch-campaigns-from-product-changelog-releases-for-x-ads
description: >-
Watches your changelog and launch calendar, and spins up X launch campaigns and copy refreshes for meaningful releases.
---
# Launch campaigns from product changelog releases for X Ads
Source: https://www.roadwayai.com/workflows/launch-campaigns-from-product-changelog-releases-for-x-ads
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
Watches your changelog and launch calendar, and spins up X launch campaigns and copy refreshes for meaningful releases.
Watches your changelog and launch calendar, and spins up X launch campaigns and copy refreshes for meaningful releases. It keeps watching for this trigger, so you can respond within hours instead of at the 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
auto_approve, experiment_budget_pct, funnel_metrics, goal_metric, max_change_pct, monthly_budget_cap, product_launches, task_history
## Prompt
Launch campaigns from product changelog releases for X Ads
Review new entries in the launch calendar since the last run and decide the X response for each:
1. Launch dedicated campaign
2. Refresh existing ad copy
3. Add to retargeting only
4. Skip
Context and defaults (use these; don't ask):
- The launch calendar: [set this to your own product launches]. If it isn't available, say so and skip the rules that depend on it.
- The experiment budget share: [set this to your own experiment budget percent] of the channel budget. If not set, 10%.
- 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:
- Launch a dedicated campaign only for releases that open a new use case, a new market, or a feature competitors lack and buyers search for or talk about. Most changelog items deserve a copy refresh at most.
- For X, a launch campaign uses keyword, conversation topic, follower look-alike (@handle), interest and custom audience targeting tied to the problem the release solves, native-sounding copy under ~100 characters, a strong first line, 1:1 or 16:9 video under 15 seconds, and replies-friendly hooks, and a launch-specific landing page.
- Refresh existing ad copy when a release removes a common objection (an integration, SSO, a price change). Add it as a headline or proof point in the relevant ad groups.
- Add to retargeting only for incremental improvements that matter to evaluating prospects and existing trial users.
- Set launch campaigns to a 2-4 week test window with the experiment budget share of the channel budget and judge them on [set this to your own goal metric] like any other campaign.
- For a major release, draft the full launch kit on every connected channel (campaign, ad groups, copy and assets) in one plan for a single approval, rather than channel by channel.
- 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:
X launch response report
Summary:
The releases reviewed, the campaigns and copy launched, and the expected impact.
Launch dedicated campaign:
- [release] - [reason]
Refresh existing ad copy:
- [release] - [reason]
Add to retargeting only:
- [release] - [reason]
Skip:
- [release] - [reason]
Copy to ship:
- [release] - [headline / post copy] - [landing page]
## Run it in Roadway
https://www.roadwayai.com/workflows/launch-campaigns-from-product-changelog-releases-for-x-ads
Watches your changelog and launch calendar, and spins up X launch campaigns and copy refreshes for meaningful releases. It keeps watching for this trigger, so you can respond within hours instead of at the next review. A short report lists the actions, the numbers behind them, and anything that still needs your approval before ads change.
