# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Refresh Thought Leader Ads when the promoted post goes stale.
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/refresh-thought-leader-ads-when-the-promoted-post-goes-stale
Page: https://www.roadwayai.com/workflows/refresh-thought-leader-ads-when-the-promoted-post-goes-stale
Library index: https://www.roadwayai.com/automation-library
---
name: refresh-thought-leader-ads-when-the-promoted-post-goes-stale
description: >-
Replaces LinkedIn Thought Leader Ads running on older posts that have stopped performing with newer posts from the same people, keeping the targeting and budget.
---
# Refresh Thought Leader Ads when the promoted post goes stale
Source: https://www.roadwayai.com/workflows/refresh-thought-leader-ads-when-the-promoted-post-goes-stale
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
Replaces LinkedIn Thought Leader Ads running on older posts that have stopped performing with newer posts from the same people, keeping the targeting and budget.
Each run, it checks your LinkedIn Thought Leader Ads for falling click-through and engagement. When one has dropped for 3 runs in a row, it finds a newer post from the same person that fits the audience and drafts the swap with the same targeting and budget. 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, cost_per_goal_baseline, employee_advocates, funnel_metrics, goal_metric, max_change_pct, min_sample_size, monthly_budget_cap, task_history
## Prompt
Refresh Thought Leader Ads when the promoted post goes stale
Check every LinkedIn Thought Leader Ad for falling click-through and engagement, look for a newer post from someone in [set this to your own employee advocates] that fits the same audience, and decide for each ad:
1. Swap in the newer post
2. Keep running
3. Retire without replacement
Context and defaults (use these; don't ask):
- Employee advocates: [set this to your own employee advocates]. If it isn't available, say so and stop. Source: a team-maintained list in a HubSpot or Notion MCP connected in Roadway.
- 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 baseline cost per goal: [set this to your own cost per goal baseline]. If not set, compute it: Roadway spend ÷ Roadway-attributed [set this to your own goal metric] for the same campaigns, and state the number.
- The minimum number of conversions: [set this to your own min sample size] goal events per variant. If not set, 30.
- 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:
- A Thought Leader Ad is stale when its click-through and engagement have fallen for 3 runs in a row and its cost per goal is above the baseline.
- Swap in the newer post: draft the swap with the new post, the same targeting and the same budget, for approval, and retire the old one once the new one is live.
- Only use posts the person has published and allowed for promotion. Don't edit their words.
- Retire without replacement when no newer post fits the audience.
- Creating new Thought Leader Ads from mentions belongs to the TLA skeleton workflow. This one refreshes the ones already running.
- 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:
Thought Leader Ads refresh report
Summary:
Stale ads found, swaps drafted, and how the new posts are doing.
Swap in the newer post:
- [Thought Leader Ad] - [reason]
Keep running:
- [Thought Leader Ad] - [reason]
Retire without replacement:
- [Thought Leader Ad] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/refresh-thought-leader-ads-when-the-promoted-post-goes-stale
Refresh Thought Leader Ads when the promoted post goes stale
Refresh Thought Leader Ads when the promoted post goes stale
Replaces LinkedIn Thought Leader Ads running on older posts that have stopped performing with newer posts from the same people, keeping the targeting and budget.
Each run, it checks your LinkedIn Thought Leader Ads for falling click-through and engagement. When one has dropped for 3 runs in a row, it finds a newer post from the same person that fits the audience and drafts the swap with the same targeting and budget. 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.