# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Launch integration campaigns when a partner lists you in their marketplace.
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-integration-campaigns-when-a-partner-lists-you-in-their-marketplace
Page: https://www.roadwayai.com/workflows/launch-integration-campaigns-when-a-partner-lists-you-in-their-marketplace
Library index: https://www.roadwayai.com/automation-library
---
name: launch-integration-campaigns-when-a-partner-lists-you-in-their-marketplace
description: >-
When a partner adds you to their app marketplace or integrations directory, drafts a search ad group on partner integration terms, partner headlines, a sitelink to your integration page and, where the platform allows, a test aimed at the partner's users.
---
# Launch integration campaigns when a partner lists you in their marketplace
Source: https://www.roadwayai.com/workflows/launch-integration-campaigns-when-a-partner-lists-you-in-their-marketplace
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 adds you to their app marketplace or integrations directory, drafts a search ad group on partner integration terms, partner headlines, a sitelink to your integration page and, where the platform allows, a test aimed at the partner's users.
Each run, it reads the marketplace and integrations pages of the partners you name and compares them with what it saw on the last run. When a partner adds a listing for you, it drafts a partner integration ad group on search, a sitelink to your integration page and, where the platform offers it, a test aimed at the partner's users. 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, cpa_guardrail, experiment_budget_pct, funnel_metrics, goal_metric, max_change_pct, monthly_budget_cap, partners, task_history, top_landing_pages
## Prompt
Launch integration campaigns when a partner lists you in their marketplace
Check the app marketplace or integrations directory of each partner in [set this to your own partners] for a listing of us that wasn't there on the last run, and for each new listing decide:
1. Launch integration ad group
2. Add partner audience test
3. Add integration sitelink only
4. Skip
Context and defaults (use these; don't ask):
- Partners and the URL of each one's app marketplace or integrations directory: [set this to your own partners]. If it isn't available, say so and stop.
- Web search: read each page with the web search tool. If a page can't be read, say which one and skip it.
- 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 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 experiment budget share: [set this to your own experiment budget percent] of the channel budget. If not set, 10%.
- The cost guardrail: [set this to your own CPA 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 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 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 new listing is a page in the partner's directory that names us and wasn't in the list you recorded in [set this to your own task history] on the last run. On the first run, record every listing you find as the starting list and act only on listings the team confirms are new.
- Launch integration ad group: on Google Search and Microsoft Bing, open an ad group on "[partner] [our category]" and "[partner] integration" terms that Keyword Planner shows have search volume, exact and phrase match only, with partner headlines and a sitelink to our integration page from [set this to your own top landing pages]. Start it at [set this to your own experiment budget percent] of the channel budget.
- Add partner audience test: on LinkedIn or Meta, only where the platform offers the partner's users as an interest or member skill, draft a test at [set this to your own experiment budget percent]. If the platform has no such audience, skip it and say so.
- Add integration sitelink only when partner terms have too little search volume for their own ad group.
- Check the partner's brand rules before using their name or logo in ads. Use only claims in [set this to your own approved claims], and mark anything else Unverified.
- This workflow reacts to a partner listing us. Launches the partner announces about their own product belong to the partner launch workflows, so don't repeat those changes.
- Cut a test when its cost per goal passes [set this to your own CPA guardrail] once it has enough spend and goal events to judge, confirmed against [set this to your own funnel metrics].
- 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 marketplace listing report
Summary:
The new listings found, the ad groups and tests drafted, and results so far.
Launch integration ad group:
- [partner listing] - [reason]
Add partner audience test:
- [partner listing] - [reason]
Add integration sitelink only:
- [partner listing] - [reason]
Skip:
- [partner listing] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/launch-integration-campaigns-when-a-partner-lists-you-in-their-marketplace
Launch integration campaigns when a partner lists you in their marketplace
Launch integration campaigns when a partner lists you in their marketplace
When a partner adds you to their app marketplace or integrations directory, drafts a search ad group on partner integration terms, partner headlines, a sitelink to your integration page and, where the platform allows, a test aimed at the partner's users.
Each run, it reads the marketplace and integrations pages of the partners you name and compares them with what it saw on the last run. When a partner adds a listing for you, it drafts a partner integration ad group on search, a sitelink to your integration page and, where the platform offers it, a test aimed at the partner's users. 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.