Trigify launches Signals beta with 16 account buying signals

Trigify's changelog for May 20, 2026 announced Signals in beta, which the company calls a new ABM engine for spotting account intent. Users track people and companies by adding profile or company URLs manually or by CSV, choose from 16 signal types across person and company activity, review a credit estimate based on the signals chosen and how often Trigify checks them, and launch. Fired signals appear on a timeline with the reason, account context, signal count and severity. A new Social Signals trigger lets teams start workflows to enrich, qualify, alert, route or create outbound when a signal fires.

The details

• Person signals include role and company changes, posting a job ad, liking competitor or tracked content, commenting on tracked content and engaging with tracked topics.
• Company signals include hiring for relevant roles, increased job counts, posting about a relevant initiative and an expansion signal.
• A separate Insights feature looks for patterns such as narrative shifts across a target account.
• Signals is enabled under Settings, Early Access, and is available through the app, API, CLI and MCP.

Context

Signals followed Trigify's April 2026 CLI and agent Skills release and earlier 2026 updates to its Jarvis assistant and X API access. In our later coverage, Trigify added news monitoring as a workflow trigger in June, redesigned its platform around Social Listening in August, and in September its team joined HubSpot as the standalone signals platform began winding down.

Not disclosed

• Credit cost per signal or check
• General availability date
• Data sources behind each signal
• Which plans can use Signals