Engagement refreshes now revisit 90 days of posts, global search reaches your content and leads, and lead webhooks are clearer, complete, and correctly qualified.
LinkedIn posts often keep attracting reactions and comments long after they are published. Embers now keeps those growing conversations in sync for longer, while making sure downstream automations receive the right people and the right context.
Keep growing posts in sync
Embers now revisits up to 90 days of your posts during the scheduled engagement refresh. This captures people who react or comment after the first scan, including activity that arrives several weeks later.
Existing workspaces receive a catch-up refresh automatically. After that, Embers revisits the full 90-day window every week and uses a smaller rolling refresh between those runs. Post engagement totals are rebuilt from the detailed reaction and comment records, so the people shown in Embers stay aligned with the activity available from LinkedIn.
Newly discovered engagers continue through ICP classification and scoring. If they qualify, they can enter the connection, messaging, or CRM workflows you already configured.
Send qualified leads to your automations
The new lead webhook now follows the same definition as the default Leads view. It is sent only when a positive-scoring engager matches your ICP or is manually approved.
People who do not match your ICP remain available in the broader engager view, but they no longer trigger a new lead webhook. This keeps connection campaigns and CRM automations focused on the prospects they were designed to reach.
Webhook delivery now waits for profile enrichment to finish, which makes role and company details more complete. Current work history and profile headlines provide additional fallbacks when LinkedIn does not return a structured job title.
Review webhook activity more easily
The Webhooks page now uses the same wider layout and pagination patterns as the rest of Embers. Delivery rows identify the person or report involved, show useful context at a glance, and support server-side filtering by status and event type.
Delivery details lead with the event summary and attempt history. Raw JSON remains available when you need it, but it stays collapsed until you choose to inspect or copy it. Older events that were created for a non-ICP engager are labeled clearly as historical engager events.
Search leads, posts, and comments from one place
Global search now searches account content instead of only matching navigation commands. Results can take you directly to a lead or comment, while broader actions open filtered views for leads, posts, and comments.
Search results include useful lead context such as names, companies, and job titles, making it easier to find someone without first opening the Leads table.
Recover agent work more reliably
Pending engagement backfills can start as soon as they are due instead of waiting for the next normal agent interval. If a server interruption happens after data is fetched, Embers now requeues normalization so that completed work is not silently discarded.
Together, these updates keep engagement counts fresher, protect lead automations from non-ICP engagers, and make it easier to understand what Embers sent and why.