# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Snapshot weekly pipeline from paid.
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/snapshot-weekly-pipeline-from-paid
Page: https://www.roadwayai.com/workflows/snapshot-weekly-pipeline-from-paid
Library index: https://www.roadwayai.com/automation-library
---
name: snapshot-weekly-pipeline-from-paid
description: >-
A weekly snapshot of pipeline created by paid channels: qualified leads, opportunities and pipeline value by channel.
---
# Snapshot weekly pipeline from paid
Source: https://www.roadwayai.com/workflows/snapshot-weekly-pipeline-from-paid
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
A weekly snapshot of pipeline created by paid channels: qualified leads, opportunities and pipeline value by channel.
A weekly snapshot of pipeline created by paid channels: qualified leads, opportunities and pipeline value by channel. It reads your live account and turns the numbers into a short written report. It is a quick weekly read. Report pipeline velocity by channel goes deeper on how fast leads move through the funnel.
## 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
attribution_model, crm_pipeline_data, goal_metric
## Prompt
Snapshot weekly pipeline from paid
Pull last week's qualified leads, opportunities and pipeline value by paid channel from [set this to your own CRM pipeline data], and classify each channel:
1. Ahead of plan
2. On plan
3. Behind plan
Context and defaults (use these; don't ask):
- The attribution model: [set this to your own attribution model]. If not set, Roadway's default attribution, stated.
Rules:
- Use opportunity creation date and source per the attribution model. Compare against the weekly plan and the 4-week average.
- List the top 5 opportunities sourced by paid, with channel and campaign.
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:
Weekly paid pipeline snapshot
Summary:
qualified leads, opportunities and pipeline by channel vs plan, and the top opportunities.
Ahead of plan:
- [channel] - [reason]
On plan:
- [channel] - [reason]
Behind plan:
- [channel] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/snapshot-weekly-pipeline-from-paid
A weekly snapshot of pipeline created by paid channels: qualified leads, opportunities and pipeline value by channel. It reads your live account and turns the numbers into a short written report. It is a quick weekly read. Report pipeline velocity by channel goes deeper on how fast leads move through the funnel.
