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.
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
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.
Extraits citables
Ce que cette documentation doit rendre explicite.
PurposeNot every event deserves an alert. The best webhooks are the ones that immediately change the next sales action.
Workflow proofPrioritize replies, accepted invitations with no message, read messages with no reply, repeat visitors, and imported leads that were never activated.
Assistant promptDesign a Yadulink webhook event plan that sends only truly actionable LinkedIn signals to my CRM and AI agents.
Méthode de vérification
Comment transformer le guide en test opérationnel.
- 01 Event mapping Select events that change priority: reply, acceptance, repeat visit, or warm signal.
- 02 Event mapping Map each event to a precise CRM action.
- 03 Event mapping Add an idempotency key to avoid duplicates in external tools.
Maillage docs
Guides à lire ensuite.
Webhooks
Yadulink webhooks: sync replies, reads, and LinkedIn signals
Turn LinkedIn events into CRM actions and sales alerts.
API
Yadulink API authentication: keys, scopes, and best practices
Use Yadulink API keys without exposing your LinkedIn account.
n8n
Automate Yadulink with n8n: LinkedIn and CRM recipes
Build n8n workflows around Yadulink LinkedIn signals.
LinkedIn data
Yadulink LinkedIn data API: signals, leads, and enrichment
Build workflows on LinkedIn signals processed by Yadulink.