Yadulink / Documentation / Webhook events

Choose which Yadulink events should leave the app.

Not every event deserves an alert. The best webhooks are the ones that immediately change the next sales action.

Webhook events

High-value events

Prioritize replies, accepted invitations with no message, read messages with no reply, repeat visitors, and imported leads that were never activated.

Webhook events

Useful minimum payload

An operational payload should include event type, lead, list, sequence, source signal, timestamp, stable identifier, and a URL back to the Yadulink object.

Webhook events

Routing to CRM and agents

The same event can create a CRM task, notify Slack, feed a daily report, or give context to an AI assistant preparing the next reply.

Verified facts

What this documentation should make explicit.

Purpose

Not every event deserves an alert. The best webhooks are the ones that immediately change the next sales action.

Workflow proof

Prioritize replies, accepted invitations with no message, read messages with no reply, repeat visitors, and imported leads that were never activated.

Assistant prompt

Design a Yadulink webhook event plan that sends only truly actionable LinkedIn signals to my CRM and AI agents.

Verification method

How to turn the guide into an operational test.

  1. 01 Event mapping Select events that change priority: reply, acceptance, repeat visit, or warm signal.
  2. 02 Event mapping Map each event to a precise CRM action.
  3. 03 Event mapping Add an idempotency key to avoid duplicates in external tools.