Signals cookbook

Each recipe is a complete request body. Cost estimates assume the 10M tier ($1.25 / 1K credits) — see Credits & billing for the full graduated curve. Remember: every Signal’s first check is the baseline — billed, never triggers.

1. Job-change alert on one person

Fire when title, position or company changes. Daily checks.

POST /v1/signals

{
  "name": "Champion moved — Jane Doe",
  "tags": ["champions"],
  "schedule": { "interval": "1d" },
  "target": { "type": "profile", "linkedin_url": "https://linkedin.com/in/janedoe" },
  "criteria": { "mode": "field_change", "fields": ["headline", "position", "company"] },
  "notify": { "webhook_url": "https://app.example.com/hooks/up2data", "webhook_secret": "whsec_..." }
}

Cost: 1 credit per check — 1 credit a day per person.

2. The fleet: job-change alerts on 1,000 champions

The flagship setup. Set the account default webhook once, then one bulk call:

POST /v1/signals/bulk

{
  "template": {
    "name_prefix": "Job change",
    "tags": ["champions", "q3-pipeline"],
    "schedule": { "interval": "1d" },
    "criteria": { "mode": "field_change", "fields": ["headline", "position", "company"] }
  },
  "targets": [
    { "type": "profile", "linkedin_url": "https://linkedin.com/in/a" },
    { "type": "profile", "linkedin_url": "https://linkedin.com/in/b" }
  ]
}

Cost: 1,000 credits per check across the fleet — 1,000 credits a day (≈ $1.25 at the 10M tier). Pause the quarter’s campaign in one call: POST /v1/signals/pause with { "tag": "q3-pipeline" }.

Want one webhook stream and one line item instead of 1,000 Signals? Use a single Signal with target.type: "profile_list" and urls: [...] — same pricing, collective management.

3. Watch anything change on a profile

Any non-volatile field (see Filtering — counters and media URLs are excluded from * by design).

POST /v1/signals

{
  "name": "Full diff — key account CTO",
  "schedule": { "interval": "7d" },
  "target": { "type": "profile", "linkedin_url": "https://linkedin.com/in/example" },
  "criteria": { "mode": "field_change", "fields": ["*"] }
}

Cost: 1 credit per check — 1 credit a week. (No notify → account default webhook.)

4. Headcount moves on an account — with a noise floor

numeric_change with a threshold: ±5% fires, weekly drift doesn’t.

POST /v1/signals

{
  "name": "Acme Corp — headcount ±5%",
  "tags": ["accounts"],
  "schedule": { "interval": "7d" },
  "target": { "type": "company", "linkedin_url": "https://linkedin.com/company/acme" },
  "criteria": { "mode": "numeric_change", "fields": [{ "name": "headcount", "min_change_pct": 5 }] }
}

Cost: 1 credit per check — 1 credit a week per account.

5. New senior openings on a company’s job board

new_entity diffs the posting set — only new matching jobs produce Triggers.

POST /v1/signals

{
  "name": "Acme hiring senior engineers",
  "schedule": { "interval": "1d" },
  "target": {
    "type": "company_jobs",
    "linkedin_url": "https://linkedin.com/company/acme",
    "filters": { "keywords": ["engineer"], "seniority": ["senior", "director"] }
  },
  "criteria": { "mode": "new_entity" }
}

Cost: 1 credit per check (board scan) — 1 credit a day.

6. Net-new leads — Sales Nav saved-search style

Watch a people search (filters or a Sales Nav URL). Fire only when new people enter the result set — same idea as Sales Navigator’s “save search to get notified of new results.”

POST /v1/signals

{
  "name": "Net-new CTOs — US mid-market SaaS",
  "tags": ["inbound-tam"],
  "schedule": { "interval": "1d", "timezone": "America/New_York", "anchor": "2026-07-10T09:00:00Z" },
  "target": {
    "type": "people_search",
    "filters": {
      "titles": ["CTO", "Chief Technology Officer"],
      "seniorities": ["cxo"],
      "company_sizes": ["51-200", "201-500"],
      "locations": ["United States"]
    },
    "max_results": 50
  },
  "criteria": { "mode": "new_entity" },
  "notify": { "webhook_url": "https://app.example.com/hooks/up2data", "webhook_secret": "whsec_..." }
}

Or paste the Sales Nav URL you already run:

"target": {
  "type": "people_search",
  "sales_nav_url": "https://www.linkedin.com/sales/search/people?query=(…)",
  "max_results": 50
}

Trigger payload (additions only by default):

{
  "event": "signal.triggered",
  "diff": {
    "added": [
      {
        "url": "https://linkedin.com/in/new-cto",
        "full_name": "Alex Rivera",
        "headline": "CTO at Example",
        "urn": "ACoAA…"
      }
    ]
  }
}

Pipe diff.added[].url into a batch enrich job if you need full profiles. Set "include_removals": true only if you also care about people dropping out of the ICP window. Cost: 2 credits per check (50 results ≈ 2 pages × 1) — 2 credits a day. Same pattern for companies: target.type: "company_search" + criteria.mode: "new_entity".

7. Posts mentioning your trigger phrase

text_match on a keyword post search — intent signals pushed to your webhook.

POST /v1/signals

{
  "name": "Salesforce-migration chatter",
  "schedule": { "interval": "6h" },
  "target": { "type": "post_search", "query": { "keywords": ["migrating off Salesforce"] } },
  "criteria": { "mode": "text_match", "field": "text", "any_of": ["migrating", "switching", "replacing"] },
  "notify": { "webhook_url": "https://app.example.com/hooks/up2data" }
}

Cost: 1 credit per check — 4 credits a day at 6h.

8. A post crosses an engagement threshold

Engagement counts are volatile-excluded from * — name them explicitly with a floor.

POST /v1/signals

{
  "name": "Launch post goes viral",
  "schedule": { "interval": "1h" },
  "target": { "type": "post", "linkedin_url": "https://linkedin.com/posts/ceo_launch-activity-7215" },
  "criteria": { "mode": "numeric_change", "fields": [{ "name": "reactions_count", "min_change_abs": 250 }] }
}

Cost: 1 credit per check — 24 credits a day at 1h; drop to 6h for 4 a day.

9. Net-new reactors (or commenters / sharers) on a post

Watch who engaged — not just the count. Pair post_reactions / post_comments / post_reposts with new_entity. Identity is the person (profile URN/URL); leave include_removals off so incomplete pages don’t false-fire removals.

POST /v1/signals

{
  "name": "New reactors on launch post",
  "schedule": { "interval": "1h" },
  "target": {
    "type": "post_reactions",
    "linkedin_url": "https://linkedin.com/posts/ceo_launch-activity-7215",
    "max_results": 100,
    "filters": { "reaction_type": "ALL" }
  },
  "criteria": { "mode": "new_entity" },
  "notify": { "webhook_url": "https://app.example.com/hooks/up2data" }
}

diff.added[] stubs include urn, url, full_name, headline (and reaction_type for reactions). Swap type to post_comments or post_reposts for the other engagement lists. Cost: 1 credit per returned engager per check (same as /v1/posts/engagement/*); empty pages free. At max_results: 100 and 1h, budget for up to 2,400 credits/day if every check returns a full set — prefer 6h/1d on viral posts.

10. Complex logic with expressions

CEL over snapshot and diff — e.g. headcount dropped ≥10% at a company you track:

POST /v1/signals

{
  "name": "Acme layoffs detector",
  "schedule": { "interval": "1d" },
  "target": { "type": "company", "linkedin_url": "https://linkedin.com/company/acme" },
  "criteria": {
    "mode": "expression",
    "expression": "has(diff.headcount) && diff.headcount.after < diff.headcount.before * 0.9"
  }
}

11. Estimate before you enable — and cap the blast radius

Spend is credits per check × how often the Signal runs. The API projects it for you: estimated_monthly_credits on every Signal, combined totals on bulk create, and a standing burn figure on GET /v1/account.

Setup	Interval	Credits per check	Run rate
100 champions, job-change	daily	100	100 credits/day
1,000 contacts, full diff	weekly	1,000	1,000 credits/week
250 accounts, headcount ±5%	weekly	250	250 credits/week
20 job boards, new-entity	daily	40 (2 each)	40 credits/day
5 people searches, net-new (50 results)	daily	20 (4 each)	20 credits/day

Then set a hard ceiling: PATCH /v1/account with monitoring.monthly_check_budget. If fleet growth ever outruns the plan, Signals pause with budget_exceeded instead of draining your enrichment balance.

Operational tips

Dedupe on trigger_id, order by check_number — retries reuse the ID, and delivery order isn’t guaranteed.
Watch for signal.paused events — insufficient credits, budget exceeded, or a dead webhook. Signals never silently skip.
Start weekly, tighten later. PATCH /v1/signals/{id} changes the interval in place — no need to recreate.
Test the plumbing: POST /v1/signals/{id}/test-webhook sends a free signed signal.test fixture (no scrape). POST /v1/signals/{id}/check-now runs a real check (billed like a scheduled check) — poll delivery status via GET /v1/webhook-deliveries/{id}.

Overview

Enrichment

Signals

Migrations

Signals cookbook

1. Job-change alert on one person

2. The fleet: job-change alerts on 1,000 champions

3. Watch anything change on a profile

4. Headcount moves on an account — with a noise floor

5. New senior openings on a company’s job board

6. Net-new leads — Sales Nav saved-search style

7. Posts mentioning your trigger phrase

8. A post crosses an engagement threshold

9. Net-new reactors (or commenters / sharers) on a post

10. Complex logic with expressions

11. Estimate before you enable — and cap the blast radius

Operational tips

​1. Job-change alert on one person

​2. The fleet: job-change alerts on 1,000 champions

​3. Watch anything change on a profile

​4. Headcount moves on an account — with a noise floor

​5. New senior openings on a company’s job board

​6. Net-new leads — Sales Nav saved-search style

​7. Posts mentioning your trigger phrase

​8. A post crosses an engagement threshold

​9. Net-new reactors (or commenters / sharers) on a post

​10. Complex logic with expressions

​11. Estimate before you enable — and cap the blast radius

​Operational tips

1. Job-change alert on one person

2. The fleet: job-change alerts on 1,000 champions

3. Watch anything change on a profile

4. Headcount moves on an account — with a noise floor

5. New senior openings on a company’s job board

6. Net-new leads — Sales Nav saved-search style

7. Posts mentioning your trigger phrase

8. A post crosses an engagement threshold

9. Net-new reactors (or commenters / sharers) on a post

10. Complex logic with expressions

11. Estimate before you enable — and cap the blast radius

Operational tips