Skip to main content
skill CX Codex

finding-podcast-hosts-for-outreach — Claude Code skill

Find podcast hosts for PR and guest pitches through Apify Twitter scrapers. Use it when you need a topic-focused outreach list.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add apidojo-io/apidojo-skills --skill finding-podcast-hosts-for-outreach -a claude-code
Open on GitHub

What finding-podcast-hosts-for-outreach does

This skill searches Twitter for episode announcements, guest references, and show-promotion activity. It gathers distinct host accounts, enriches their profiles, and returns signals such as the show name, topic, follower count, and audience size. The result is structured for outreach planning.

Its workflow covers discovery, host filtering, profile enrichment, priority scoring, and delivery of the final list. The included scripts/run_actor.js runner can print a table or write CSV and JSON files. It uses apidojo~tweet-scraper and apidojo~twitter-user-scraper; APIFY_TOKEN must be available in the environment or .env, or the actors cannot run. An Apify MCP server is optional.

The scoring logic checks guest-format signals, recent episode activity, follower range, and topic fit. It also flags accounts that share a show without hosting it, large media-company podcasts, and hosts whose activity has gone quiet.

What it helps with

  • find podcast hosts in a target niche
  • build an outreach list from Twitter activity
  • separate hosts from accounts that only share shows
  • rank podcasts for guest-pitch priority
  • export the results as CSV or JSON

Example prompts for the agent

  • Find podcast hosts who cover fintech and could take a guest pitch.
  • Search Twitter for startup episode announcements, verify the hosts, and save the outreach list as CSV.
  • Review the profiles for guest-format signals and rank them by outreach priority.

How to install finding-podcast-hosts-for-outreach

1Skills CLI (Vercel)

npx skills add apidojo-io/apidojo-skills --skill finding-podcast-hosts-for-outreach -a claude-code

2Manually: put the files in place

~/.claude/skills/finding-podcast-hosts-for-outreach/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/finding-podcast-hosts-for-outreach/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about finding-podcast-hosts-for-outreach

How do I install finding-podcast-hosts-for-outreach in Claude Code?

Run npx skills add apidojo-io/apidojo-skills --skill finding-podcast-hosts-for-outreach -a claude-code, then use ~/.claude/skills/finding-podcast-hosts-for-outreach/SKILL.md.

What does finding-podcast-hosts-for-outreach do?

It discovers podcast hosts through Twitter activity, enriches their profiles, and prepares a list for PR or guest outreach. The output includes host handles, show details, topic focus, and audience signals.

What does the skill require to run Apify actors?

Set APIFY_TOKEN in the environment or in .env. The Apify MCP server can be added as an optional route for running the actor.

Source text

SKILL.md · Apache-2.0
---
name: finding-podcast-hosts-for-outreach
description: >
  Finds podcast hosts for PR and guest outreach using apidojo's Twitter scrapers on Apify.
  Triggers when the user asks to: find podcast hosts to pitch for a guest spot, discover podcasters
  in a niche for PR outreach, build a podcast outreach list from Twitter, find podcast hosts who
  cover a specific topic or industry, identify podcasters who interview guests in a business niche,
  find B2B podcast hosts for thought leadership placement, or compile a list of podcast hosts
  for a media relations campaign.
  Returns podcast host handle, show name, topic focus, follower count, and audience size signals.
  Ideal for PR agencies, executives doing thought leadership, authors, and startup founders.
license: Apache-2.0
metadata:
  author: apidojo
  version: "1.0"
  apify-actors: apidojo/twitter-user-scraper, apidojo/tweet-scraper
---

# Finding Podcast Hosts for Outreach

Discovers podcast hosts on Twitter by episode announcements, guest mentions, and show promotion signals.

## Prerequisites

- `APIFY_TOKEN` environment variable set
- Optional: Apify MCP server installed

## Inputs

| Parameter | Type | Required | Default | Notes |
|-----------|------|----------|---------|-------|
| `startUrls` | array | Optional | `[]` | Twitter profile or tweet URLs |
| `twitterHandles` | array | Optional | `[]` | Twitter usernames (without @) |
| `twitterUserIds` | array | Optional | `[]` | Twitter user IDs |
| `getFollowers` | boolean | Optional | `false` | Extract follower lists |
| `getFollowing` | boolean | Optional | `false` | Extract following lists |
| `getRetweeters` | boolean | Optional | `false` | Extract retweeters of a tweet URL |
| `includeUnavailableUsers` | boolean | Optional | `false` | Include unavailable/suspended users |
| `maxItems` | number | Optional | Unlimited | Maximum users to return |
| `customMapFunction` | string | Optional | — | JavaScript function to transform each output object |

## Workflow

```
Progress:
- [ ] Step 1: Search for podcast announcement tweets
- [ ] Step 2: Collect unique host handles
- [ ] Step 3: Enrich host profiles
- [ ] Step 4: Score outreach priority
- [ ] Step 5: Deliver podcast outreach list
```

### Step 1: Search Queries


**Recommended — run_actor.js (handles waiting, output, and file saving automatically):**
```bash
# Quick answer (prints table to chat)
node scripts/run_actor.js \
  --actor "apidojo~twitter-user-scraper" \
  --input '{"param": "value"}'

# Save as CSV
node scripts/run_actor.js \
  --actor "apidojo~twitter-user-scraper" \
  --input '{"param": "value"}' \
  --output YYYY-MM-DD_results.csv --format csv

# Save as JSON
node scripts/run_actor.js \
  --actor "apidojo~twitter-user-scraper" \
  --input '{"param": "value"}' \
  --output YYYY-MM-DD_results.json --format json
```
> `APIFY_TOKEN` must be set in environment or `.env` file.

**If Apify MCP is available:**
```
Tool: apify:run-actor
Actor: "apidojo~tweet-scraper"
Input:
{
  "searchTerms": ["[TOPIC] podcast", "new episode [TOPIC]", "podcast host [TOPIC]"],
  "maxItems": 300
}
```

**REST API fallback:**
```bash
curl -X POST \
  "https://api.apify.com/v2/acts/apidojo~tweet-scraper/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"searchTerms": ["entrepreneurship podcast", "new episode startup"], "maxItems": 300}'
```

### Step 2: Enrich and Filter

Run `apidojo~twitter-user-scraper` on handles. Keep profiles where bio contains "podcast", "host", "show", "episodes".

**Guest format:** bio or tweets mention "guest", "interview", "this week's guest" → `has_guest_format = true`

### Step 3: Score Outreach Priority

```
outreach_score = (has_guest_format ? 1 : 0.3) * 0.35
               + (tweeted_episode_in_last_30_days ? 1 : 0) * 0.25
               + (followerCount in 1000..100000 ? 1 : 0.6) * 0.25
               + (topic_alignment: strong=1, weak=0.5) * 0.15
```

### Step 4: Edge Cases

- **Account shares content but is not host**: Verify bio says "host" — some accounts share show content without hosting
- **Show name not findable**: Note as `show_name_unknown`; LinkedIn search needed
- **Large media company podcast**: Flag as `PREMIUM_PLACEMENT` — A-list guests only

## Output Format

```
# Podcast Host Outreach List: [TOPIC]
Hosts found: [N] | Guest-format: [N] | Active: [N] | Date: [DATE]

## Priority (Guest-Format + Active + Mid-Tier)
| Host | @Handle | Show | Followers | Last Episode | Score |
|------|---------|------|-----------|-------------|-------|

## Small Shows (Easier to Land)
| Host | @Handle | Followers | Last Active |
|------|---------|-----------|------------|

## Personalization Tip
Reference the host's most recent episode topic in your pitch — hosts receive dozens of pitches, relevance is the strongest differentiator.
```

## Troubleshooting

**Results include listeners not hosts**: Require "podcast host" OR "host of [show]" in bio.
**No show found on Twitter**: Supplement with Spotify/Apple Podcasts search.
**Host inactive > 60 days**: Flag as potentially on hiatus; verify before pitching.

© apidojo · Apache-2.0 · apidojo-io/apidojo-skills

Similar skills

Everything for Marketing and content →

From the same set82

finding-tiktok-shop-trending-products Detects viral TikTok Shop merchandise using Apify scrapers. It calculates creator density, tracks engagement metrics, and flags saturated niches before sourcing. CX Codex +1 785installs tracking-sports-team-fan-sentiment-twitter Collects tweets about a sports team and measures fan sentiment. Use it to study reactions to games, team news, player trades, and events. CX Codex +1 785installs analyzing-competitor-twitter-profile-content This skill pulls a competitor's or brand's tweet history through Apify and ranks posts by engagement. Useful when you need to see what a rival actually posts. CX Codex +1 784installs finding-food-bloggers-and-creators Discovers food creators across Instagram, TikTok, and YouTube using Apify scrapers. Segments influencers by engagement, niche, and content themes. CX Codex +1 782installs building-journalist-outreach-list-from-twitter Builds journalist and media contact lists for a given beat by scraping Twitter/X through Apify. Useful when you need names before a press pitch. CX Codex +1 780installs scraping-tiktok-comments Exports the comment dataset of any TikTok video through apidojo's scraper on Apify: author, text, likes, replies, timestamp. Handy when you need to read what viewers actually wrote. CX Codex +1 778installs discovering-viral-tiktok-content-trends This skill finds viral TikTok formats in a chosen niche and breaks down hashtags, reach, engagement, and hooks. Use it when planning content angles. CX Codex +1 777installs analyzing-competitor-youtube-content-strategy Audits a competitor’s YouTube strategy by topic, format, publishing cadence, views, and engagement. Use it to compare two channels or find content gaps. CX Codex +1 776installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor