Signals overview · Client Path Docs

A signal is an external event relevant to a client you are tracking. Signals are produced by signal sources, which are integrations that poll external data providers on a schedule.

When a signal arrives for a client, Client Path creates a signal_event Activity and evaluates any automations with the signal_event trigger.

Why signals matter

Research runs give you a point-in-time view of a prospect. Signals give you the continuous layer: events that happen after the initial research that might change the picture.

A funding announcement, a leadership hire, or a product launch can all be signals that a prospect is now more (or less) ready to buy. With a signal_event automation, you can automatically re-research the client or draft outreach the moment a relevant signal arrives.

Signal anatomy

Each signal has:

Source: which integration produced it (for example, company-news).
Kind: the event type within that source (for example, funding, leadership_change, product_launch).
Client: the client the signal is about.
Payload: structured data from the source (varies by source and kind).
Arrived at: when Client Path received the signal.

Signal events and the activity feed

When a signal arrives, a signal_event Activity is created on the client record. You can see recent signals in the client's activity feed.

Feeding automations

The signal_event trigger fires on every new signal. Use the trigger's condition to filter which signals actually fire the automation — for example, only fire when the signal kind is funding and the client's current propensity score is above 50.