Skip to main content
Raw signals is one list of everything the prospects you track did, and everything your network did with them. Warm intros, Accounts and scores are built on top of it; this is the layer underneath. Open it from Network ▸ Raw signals in the sidebar.

​
How a row reads

Every row is about one prospect, the Subject. It is never your connector: when one of your connectors engaged a prospect’s post, the row is still about the prospect, and the sentence says who engaged. The columns are When, Subject, Signal, What happened and Source, and every row fills all five.
  • When: the exact date and time it happened. Newest first by default; sort either way from the header.
  • Subject: the prospect, with their role and company. The name opens their record.
  • Signal: what kind of signal it is, as family and type, for example Network · Reaction or Activity · Post.
  • What happened: one sentence, with the other person in bold and a short quote of the post or comment. The other person’s name opens their record, the post’s reactions, comments and shares sit on the right, and the link mark opens the post.
  • Source: where it was seen. LinkedIn today.

​
Signal families

What the sentence says depends on who started it: When Clustr has not read the post yet, the sentence stops at “Reacted to a post” or names the connector on the path. The same reaction can count for several of your warm intros. It shows once, and its detail panel lists every warm intro it feeds. Several reactions from one person on one post also show once.

​
The detail panel

Click a row to open its signal. The panel shows:
  • the whole post or comment, and a link to open it on LinkedIn;
  • the other person, who they are to you (one of your connectors, another prospect, or the post’s author), and a link to their record;
  • the other signals on the same post among the rows loaded;
  • every warm intro this signal feeds, each with Open warm intro;
  • the raw details (type, direction, source and ids), folded away.
The open signal is in the page address, so a copied link opens it.

​
Filters, sorting and views

The table works like Warm intros and Accounts: + Add filter, a column header’s menu, or the search box, which looks through comment text.
  • When (with Last 7, 30 and 90 days).
  • Signal family and Signal type.
  • Origin: Prospect-initiated (the prospect reacted, commented or posted) or Network-initiated (one of your connectors engaged the prospect’s post).
  • Involves: a connector on the other side of the interaction.
  • Person and Account, the account’s industry, company size, revenue, HQ country, tier, tags and owner (the same filters as Accounts), the tags on the account’s warm intros (Warm intro tags), and seniority (the same filter as Warm intros).
  • Source.
Save a filtered list as a view the same way as on the other tables; it shows as a pill above the list. Filters, sort and the open signal are all in the page address.

​
Export

Export current view in the ⋯ menu downloads a CSV of the rows your filters select, up to 50,000 rows, with the signal family, type, origin and the sentence beside every raw field. If more rows match, the file holds the 50,000 most recent and the app tells you so: narrow When and export again for the rest. Tick rows to export only those.

​
From your AI assistant

The MCP server has list_signals (new in v1.29.0). It takes:
  • since and until: a day such as 2026-09-01, or a full ISO-8601 time.
  • families: network, activity, prospect.
  • origins: prospect or network.
  • types: reaction, comment, post, repost.
  • The account filters industries, employees, revenues, countries, tiers, owners and tags, path_tags (the tags on the account’s warm intros), and seniority_ranks (0 intern to 7 C-suite).
  • order: desc (default, newest first) or asc.
  • limit and offset for paging.
Each row carries family, origin, the post it was about (post_text, post_author_name) and opportunity_id, which get_opportunity reads.