lexisOS
Setting things up…
Setting things up…
Loading features…
Three signal kinds — a role change, a company change, or a keyword match in a LinkedIn post — each configured with its own schema.
| Signal kind | What it watches for | What you configure |
|---|---|---|
| Role change | A tracked person’s job title or seniority changes. | A seniority floor and a company allow-list. |
| Company change | A tracked person moves to a different company. | No fields beyond the population it watches. |
| Post keyword | A tracked person’s LinkedIn post matches a keyword. | A list of keywords to match against. |
Set a seniority floor and company allow-list for a role change, or a keyword list for a post match.
The signal runs on its schedule and records a match the moment its condition is met.
Every match shows up in a feed joined directly to the underlying Lead or Contact — not a separate list you cross-reference by hand.
A signal is one of the workflow trigger types — a match can start a connect, message, email, or any other step automatically.
Signals sits behind its own feature gate, and that gate is enforced on every route — including the read paths, not only the ones that create or edit a signal. That closes a gap an earlier version of the code left open: an org whose Signals access had lapsed could otherwise still read matches through a direct API call, even with the module switched off in the interface.
“The signal watches. The workflow — and its own approval setting — decides what happens next.”
Start free and configure your first signal — a role change, a company change, or a keyword match, each with its own schema.