---
name: add-creator-sources
description: Turn LinkedIn creators whose audience matches the ICP into CampaignStack signal sources. Use when lead flow slows down, after a lead-magnet discovery run, or when someone says "find new sources" or "add these creators".
---

# Add creator sources

A creator whose posts draw the ICP is a source: a `profile_feed` signal agent
watches their new posts and brings the people who engage into a workflow.
Discovery finds candidates. This skill turns the right ones into sources.

## 1. Are sources running dry?

`campaignstack_get_signal_agents` lists the agents with their `status` and
`workflowId`. For each active one, find the `signal:intake` node
(`campaignstack_get_workflows(ids: [workflowId], include: {graph: {}})`), then
read its newest entries (`nodes: {ids: [<intake node id>]}`,
`include: {nodeActivity: {}}`). Go by the entry dates: the node's `stats` count
all time. A creator bringing fewer than about one new person a day, or nobody
in two weeks, is running dry. Say which.

## 2. Read discovery

`campaignstack_get_lead_magnets(include: {posts: true, creators: true, runs: true, settings: true})`.
The settings item's `schedule.topics` are the weekly discovery topics. If they
are vague, propose sharper ones around what the workspace sells
(`campaignstack_edit_lead_magnets`, op `schedule` with `enabled` and `topics`).
Turning the schedule on needs `confirmRecurringCost: true`: it runs a
100-credit search every week until someone turns it off. A one-off run is
`campaignstack_discover_lead_magnets(mode: "topic_search", topics: [...], confirmCost: true)`
and costs 100 credits. Say the cost and wait for a yes before either.

## 3. Pick the creators

Read the offer first (`campaignstack_get_workspaces(include: {playbook: {}})`)
and the ICP (`campaignstack_get_campaigns(include: {icp: {}})`). Keep a creator
when their posts:
- are about the problem the workspace solves, or
- give away something that replaces a role the product fills (for an
  outreach tool: SDR, appointment setter, prospecting assistant).

Drop audiences of job seekers, very large general audiences, unrelated
niches and creators already watched. Pick by these rules, not by taste. Show
the list (name, profile, the post that matched, why) and wait for a yes.

## 4. Resolve each profile

`campaignstack_get_leads(query: "<name>")` gives
`profiles.linkedin.externalId`, the bare member id. A name search can return
someone else: check the profile URL is the creator's. If the lead is missing, import it
(`campaignstack_import_leads(rows: [{linkedInUrl: "<profile url>"}])`) and read
it again once enriched.

## 5. Create the agents

List the connected LinkedIn accounts (`campaignstack_get_accounts`). With more
than one, ask which accounts read and which send. With one, use it for both.
Ask whether the agent may reply publicly to comments (default no). Then one
`campaignstack_edit_signal_agent` call with one `create` operation per creator:

```
{operations: [{mode: "create", type: "profile_feed", name: "<Name> - Post Signals",
 target: {platform: "linkedin", kind: "profile",
          urn: "urn:li:fsd_profile:<externalId>", url: "<profile url>"},
 targetName: "<Name>", approvalMode: "manual_review",
 accountIds: [<read>], actAccountIds: [<send>],
 publicReplyConfig: {<each send account id>: false}}]}
```

`publicReplyConfig` is keyed by send account. A missing key counts as yes, so
"no" means `false` for every send account.

`actAccountIds: []` collects people but cannot send until someone adds a
sending account. Use it to audit a creator's audience before committing.

## 6. Check it runs

Within about an hour, `campaignstack_get_signal_agents(ids)` should show a
`lastPollAt`. If it stays empty, the agent's status explains why (for example
no reading account). Report what was added, what was skipped and why.
