Know what just happened at the companies you sell to: funding, acquisitions and mergers, new locations, leadership changes, product launches, contracts and partnerships, layoffs and restructuring - and the trade shows they are about to exhibit at.

Use it on the accounts you are working: a new site, a new leader or a deal is the moment priorities and suppliers get revisited, and a dated fact is a better opening line than a generic follow-up.

Input: companies (a name, a domain, or a LinkedIn company URL per entry; a domain gives the most reliable match), eventTypes (empty = every type except event_participation, which you add by listing it), maxEventAgeDays (only deliver events from the last N days, default 90), cadenceDays (how often each company is checked, 14-90, default 30), plus optional persona targeting (enablePersonaTargeting, targetPersonas, maxLeadsPerCompany) and enrichment flags.

Output: one company-level lead per event. The event travels on the signal block: news_event_type (the field to switch on), news_event_date, news_headline, news_url (the article it was checked against), news_title (the article's title) and news_summary (a short account of what the article says - what happened, who is involved, figures, stated plans - to ground an outreach message without opening the article). For event_participation (the company will exhibit or speak at an upcoming trade show or conference), news_event_name and news_event_location name the show and where it is held, and news_event_date is the day it starts - so you can book the meeting on the stand before the show, not after it.

What is checked before an event reaches you. The article must be about THIS company (its website appears in the article; or its exact name together with its home city; or, for a name distinctive enough not to be shared, that exact name — a namesake elsewhere does not qualify). Companies are also followed under the brand names and websites they trade under, so news reported under a brand reaches whoever listed the legal entity behind it. The date is read from the article body and must fall inside your window (an old event re-published this week does not qualify; a trade show must still be ahead), and the event must be one of the types you asked for. The same event reported by several outlets is delivered once. news_event_date is given to the month (YYYY-MM) when the article does not state the day.

Persona targeting changes WHAT you receive; it does not add to it. Turned on, the company-level lead is REPLACED by one lead per matching person at the company, so one event can deliver several payloads, or none. Persona leads are billed per person found.

companies is consumed into the watchlist, so it is NOT echoed back in the config of this or any later response. Read what is watched with GET /api/v1/watchlists/{signalId}/companies, and add or remove companies with POST / DELETE on the same path.

Use cases:

• Open with a fact, not a follow-up - a new branch, a new VP or a closed deal at an account you are working is the reason to call this week, and the date is on the lead.
• Catch the reorganisation - an acquisition, a restructuring or a leadership change puts suppliers and tools back under review; hear it while the decision is still open.
• Keep account plans current - push every verified event into the CRM record so the account owner sees what changed without reading the trade press.
• Meet them on the show floor - when an account announces its booth at an upcoming trade show, book the meeting before the show fills their calendar.

{
  "config": {
    "cadenceDays": 30,
    "companies": [
      "acmesupply.com",
      {
        "domain": "doctolib.fr",
        "linkedinUrl": "https://www.linkedin.com/company/doctolib",
        "name": "Doctolib"
      },
      "https://www.linkedin.com/company/lemlist"
    ],
    "eventTypes": [
      "funding",
      "mergers_acquisitions",
      "expansion",
      "leadership_change"
    ],
    "maxEventAgeDays": 90
  },
  "dailyLeadLimit": 20,
  "name": "News at my accounts",
  "status": "active",
  "webhookUrl": "https://example.com/webhooks/rodz"
}

{
  "applied": {
    "allowUnknownCompanySize": false,
    "maxJobAgeDays": 180
  },
  "config": {
    "companySizeFilters": [
      "201-500",
      "501-1000"
    ],
    "getEmails": true,
    "jobTitles": [
      "CTO"
    ],
    "locations": [
      "France"
    ],
    "maxJobAgeDays": 90
  },
  "createdAt": "2026-01-15T10:30:00Z",
  "dailyLeadLimit": 50,
  "duplicateHandling": "refuse",
  "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "lastLeadAt": "2026-03-15T14:22:00Z",
  "leadsToday": 3,
  "leadsTotal": 127,
  "name": "CTOs changing jobs in France",
  "signalTypeId": "job_changes",
  "status": "active",
  "updatedAt": "2026-03-16T08:00:00Z",
  "warnings": [
    {
      "code": "VALUE_BELOW_MINIMUM",
      "field": "maxJobAgeDays",
      "message": "`maxJobAgeDays` is 90; this signal applies 180. Job changes are delivered up to 180 days after the start date, and a shorter window is raised to that minimum.",
      "severity": "info",
      "values": [
        "90"
      ]
    }
  ],
  "webhookUrl": "https://your-server.com/webhooks/rodz"
}