Dasha
05/14/2026, 4:53 PMlinkedin_account_alerts
Hey everyone! š
We've shipped a new webhook event that lets you stay on top of LinkedIn account health in real time. Instead of finding out after a sequence stalls, you'll get notified the moment something needs attention.
What you'll be alerted about:
⢠š Sales Navigator disconnected - reconnect needed to keep InMail steps running
⢠š¬ InMail credits depleted - the account can't send InMails until credits renew
⢠š Weekly connection request limit reached - sending resumes after LinkedIn resets the quota
Why this matters:
Build automations that auto-pause sequences, ping the account owner in Slack, open a ticket, or trigger any custom recovery flow, no more silent failures.
Example payloads:
Sales Navigator disconnected
{
"event": {
"date": "2026-05-13T10:45:46.3926107Z",
"id": "22ff637a-fd81-40ba-b597-0c8f26189dca",
"type": "linkedin_account_alerts",
"user_id": 12345,
"team_id": 67890,
"subscription_id": 492
},
"workspace_id": 67890,
"workspace_name": "Default Team",
"linkedin_owner_name": "Jane D.",
"linkedin_owner_email": "<mailto:jane.d@example.com|jane.d@example.com>",
"linkedin_id": 262,
"linkedin_name": "Jane Doe",
"linkedin_account_alert": "Sales Navigator is disconnected. Please reconnect your LinkedIn account to continue sending InMail steps.",
"sequence_fields": {}
}
InMail credits depleted
{
"event": {
"date": "2026-05-13T10:47:16.6543506Z",
"id": "7227258a-8624-410a-bf6c-bd5197810d66",
"type": "linkedin_account_alerts",
"user_id": 12345,
"team_id": 67890,
"subscription_id": 492
},
"workspace_id": 67890,
"workspace_name": "Default Team",
"linkedin_owner_name": "Jane D.",
"linkedin_owner_email": "<mailto:jane.d@example.com|jane.d@example.com>",
"linkedin_id": 262,
"linkedin_name": "Jane Doe",
"linkedin_account_alert": "InMail credits are used up ā this account can't send InMails until credits renew.",
"sequence_fields": {}
}
Weekly connection limit reached
{
"event": {
"date": "2026-05-13T10:47:27.4486303Z",
"id": "654258f1-a426-4d3c-96a2-b3da5f78af29",
"type": "linkedin_account_alerts",
"user_id": 12345,
"team_id": 67890,
"subscription_id": 492
},
"workspace_id": 67890,
"workspace_name": "Default Team",
"linkedin_owner_name": "Jane D.",
"linkedin_owner_email": "<mailto:jane.d@example.com|jane.d@example.com>",
"linkedin_id": 262,
"linkedin_name": "Jane Doe",
"linkedin_account_alert": "Weekly connection request limit reached. Sending new connection requests will resume after LinkedIn resets the quota.",
"sequence_fields": {}
}
š Full docs: https://docs.reply.io/webhook-event-payloads#linkedin_account_alerts
Would love to hear what you build with it, drop a comment or share your workflow! šlinkedin_account_alerts Webhook
Hey everyone! š
Quick heads-up: we've updated the payload for the linkedin_account_alerts webhook to bring it in line with our other webhooks. This is already live in production, so if you're consuming this event, please check your integrations.
What changed:
⢠ā *Removed:*`workspace_id` ā it duplicated team_id, which is already in the payload
⢠š *Renamed:*`workspace_name` ā team_name ā for naming consistency across webhooks
Updated payload example:
json
{
"event": {
"date": "2026-05-21T09:30:55.8384457Z",
"id": "e7f893b1-5ec5-4ca8-ab5e-20514bb0bbbd",
"type": "linkedin_account_alerts",
"user_id": 485874,
"team_id": 100,
"subscription_id": 19313
},
"team_name": "Test Workspace",
"linkedin_owner_name": "Test LinkedIn Owner",
"linkedin_owner_email": "<mailto:test-li-owner@example.com|test-li-owner@example.com>",
"linkedin_id": 50,
"linkedin_name": "Test LinkedIn Account",
"linkedin_account_alert": "Sales Navigator is disconnected. Please reconnect your LinkedIn account to continue sending InMail steps.",
"sequence_fields": {}
}
Action required: If your integration reads workspace_id or workspace_name, swap them for team_id and team_name.
š Docs: https://docs.reply.io/webhook-event-payloads#linkedin_account_alerts
Questions? Drop them in the thread. š