# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Flag creators who already mention you as partnership ad candidates.
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/flag-creators-who-already-mention-you-as-partnership-ad-candidates
Page: https://www.roadwayai.com/workflows/flag-creators-who-already-mention-you-as-partnership-ad-candidates
Library index: https://www.roadwayai.com/automation-library
---
name: flag-creators-who-already-mention-you-as-partnership-ad-candidates
description: >-
Lists the creators who talk about you organically and get real engagement, found with web search, so your team can ask for partnership ad or Spark Ad access. It never contacts anyone.
---
# Flag creators who already mention you as partnership ad candidates
Source: https://www.roadwayai.com/workflows/flag-creators-who-already-mention-you-as-partnership-ad-candidates
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
Lists the creators who talk about you organically and get real engagement, found with web search, so your team can ask for partnership ad or Spark Ad access. It never contacts anyone.
Each run, it uses web search, or a social listening MCP if you have one, to find public posts about you from creators. When a post does well above that creator's usual engagement, it adds them to a shortlist for your team. It doesn't contact anyone or run ads until a creator is added to your partner list. It checks for its trigger on every scheduled run, so you can act on it then instead of waiting for your next review. You get a short report with the numbers behind every line, so you can check it yourself.
## 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
creator_partners, funnel_metrics, goal_metric, icp, linkedin_mentions, slack_delivery, social_mentions, task_history
## Prompt
Flag creators who already mention you as partnership ad candidates
Read [set this to your own social mentions] and [set this to your own linkedin mentions] for public creator posts about us, compare each post's engagement with that account's usual posts, and decide for each creator not in [set this to your own creator partners]:
1. Shortlist for partnership ads
2. Watch
3. Skip
Context and defaults (use these; don't ask):
- Social mentions: [set this to your own social mentions]. If it isn't available, say so and skip the rules that depend on it. Source: public posts the agent can read with the web search tool, or a connected social listening MCP. Roadway has no native Meta, X or Reddit mention feed, so web search can miss posts; say how many you could read.
- LinkedIn mentions: [set this to your own linkedin mentions]. If it isn't available, say so and skip the rules that depend on it. Source: public LinkedIn posts the agent can read with the web search tool. Roadway has no native LinkedIn mention feed.
- Creators with partnership ad permissions: [set this to your own creator partners]. If it isn't available, treat every creator you find as new. Source: a team-maintained creator list in a Notion or HubSpot MCP connected in Roadway.
- The ideal customer profile: firmographics, roles, pains: [set this to your own ICP]. If it isn't available, say so and skip the rules that depend on it.
- The delivery channel: [set this to your own slack delivery]. If Slack isn't connected, deliver in the run's thread.
Rules:
- A creator qualifies when a public post about us gets engagement well above that account's usual posts, they aren't in [set this to your own creator partners], and the content fits [set this to your own ICP] and the brand.
- Shortlist: send the public handle, post link, engagement against their usual level, and fit with [set this to your own ICP] to [set this to your own slack delivery].
- Never contact anyone, and never run ads with their content until the team adds them to [set this to your own creator partners] and they grant partnership ad or Spark Ad access.
- Use only public business information: the handle and the post. Nothing else about the person.
- Skip posts that are negative, inaccurate or off-brand.
- Judge everything on Roadway's full-funnel measurement ([set this to your own funnel metrics]), not platform-reported conversions, and check [set this to your own task history] so you don't repeat a finding the team already acted on. This workflow doesn't change budgets, bids or ads.
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:
Creator partnership shortlist
Summary:
Creators found, how many posts web search could read, and the shortlist sent.
Shortlist for partnership ads:
- [creator] - [reason]
Watch:
- [creator] - [reason]
Skip:
- [creator] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/flag-creators-who-already-mention-you-as-partnership-ad-candidates
Flag creators who already mention you as partnership ad candidates
Flag creators who already mention you as partnership ad candidates
Lists the creators who talk about you organically and get real engagement, found with web search, so your team can ask for partnership ad or Spark Ad access. It never contacts anyone.
Each run, it uses web search, or a social listening MCP if you have one, to find public posts about you from creators. When a post does well above that creator's usual engagement, it adds them to a shortlist for your team. It doesn't contact anyone or run ads until a creator is added to your partner list. It checks for its trigger on every scheduled run, so you can act on it then instead of waiting for your next review. You get a short report with the numbers behind every line, so you can check it yourself.