# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Add target accounts that are hiring for the team you sell to.
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/add-target-accounts-that-are-hiring-for-the-team-you-sell-to
Page: https://www.roadwayai.com/workflows/add-target-accounts-that-are-hiring-for-the-team-you-sell-to
Library index: https://www.roadwayai.com/automation-library
---
name: add-target-accounts-that-are-hiring-for-the-team-you-sell-to
description: >-
Asks Clay which accounts in your ICP just posted jobs for the team your product serves, and adds them to LinkedIn company targeting with a message for a team that is growing. Needs the Clay MCP connected in Roadway.
---
# Add target accounts that are hiring for the team you sell to
Source: https://www.roadwayai.com/workflows/add-target-accounts-that-are-hiring-for-the-team-you-sell-to
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
Asks Clay which accounts in your ICP just posted jobs for the team your product serves, and adds them to LinkedIn company targeting with a message for a team that is growing. Needs the Clay MCP connected in Roadway.
Each run, it asks Clay which companies that fit your ICP just posted jobs for the team your product serves. Companies not already on your target list are added to a LinkedIn company targeting test with a message for a growing team, and flagged for sales in Slack. Every lookup uses Clay credits, so a run checks at most 25 companies. 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, funnel_metrics, goal_metric, icp, max_change_pct, monthly_budget_cap, slack_delivery, target_accounts, task_history
## Prompt
Add target accounts that are hiring for the team you sell to
Use the Clay MCP to find companies that fit [set this to your own ICP] and posted new jobs for the roles our product serves since the last run, check them against [set this to your own target accounts], and decide for each company:
1. Add to company targeting
2. Flag for sales only
3. Skip
Context and defaults (use these; don't ask):
- Clay: use the Clay MCP connected in Roadway. Clay answers only when asked and sends no alerts, and every lookup uses Clay credits. If it isn't connected, say so and stop.
- 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 target account list: [set this to your own target accounts]. 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.
- 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 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 company qualifies when it fits [set this to your own ICP], posted new jobs for the team our product serves since the last run, and isn't already in [set this to your own target accounts].
- Check at most 25 companies per run, because every Clay lookup uses credits.
- Add to company targeting: add the company to a LinkedIn company targeting test with a message for a growing team, and flag it for sales in [set this to your own slack delivery].
- Flag for sales only when the LinkedIn audience would be too small to deliver.
- Company names and domains only. Don't look up or track individual people.
- New leaders and funding rounds belong to the champion and funding workflow. This one uses hiring.
- 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:
Hiring signal account report
Summary:
Companies hiring for the team you sell to, accounts added, and accounts flagged for sales.
Add to company targeting:
- [company] - [reason]
Flag for sales only:
- [company] - [reason]
Skip:
- [company] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/add-target-accounts-that-are-hiring-for-the-team-you-sell-to
Add target accounts that are hiring for the team you sell to
Add target accounts that are hiring for the team you sell to
Asks Clay which accounts in your ICP just posted jobs for the team your product serves, and adds them to LinkedIn company targeting with a message for a team that is growing. Needs the Clay MCP connected in Roadway.
Each run, it asks Clay which companies that fit your ICP just posted jobs for the team your product serves. Companies not already on your target list are added to a LinkedIn company targeting test with a message for a growing team, and flagged for sales in Slack. Every lookup uses Clay credits, so a run checks at most 25 companies. 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.