LinkedIn

LinkedIn conversations, in the same inbox

Connect LinkedIn, messages and your page inbox, from Connections and the conversations arrive beside WhatsApp, Instagram and email, with the same assignees, routing, tickets and audit trail. The public API lists chats and manages assignments for every channel; sending on LinkedIn is worked from the inbox today.

Messages and page inbox ✦ Same queue, routing and tickets ✦ Chats and assignments by API

list-chats.sh

            
Run200 · 2 chatsGET /api/wp-crm/chats
Acme Hotels
Webhooksyourapp.com/hooks/lodgestory

The most guest-obsessed brands trust Lodgestory to power 50M+ conversations a year

Bombay Shaving Company ELIVAAS Lyskraft COYU BBingo Hotels Bloom Hotels
Connect

Connected from the same page as every channel

LinkedIn appears in Connections alongside Instagram, Messenger, WhatsApp, the web widget and push: messages and the page inbox, each with its connection status and last sync. Conversations land in the unified inbox, where the team claims them, moves them through the workflow, raises tickets and leaves notes, exactly as on any other channel.

  • Role-scoped like every channel: agents see their own and their teams' chats.
  • Tickets and notes attach to a LinkedIn conversation the same way.
  • Assignment events fire for LinkedIn chats like any other.
Connections in the docs
ConnectionsSettings · Acme Hotels
Instagram · acmehotelsConnected · comments on
Messenger · Acme HotelsConnected
LinkedIn · messages and page inboxConnecting…
Inbox6 open

Why teams build on it

Work it in one queue

LinkedIn messages and your page inbox sit in the same list as WhatsApp, Instagram, Messenger, email and calls.

Route and assign by API

List chats on the LinkedIn channel, assign people or teams, set the primary, from the API or your AI assistant.

Hear ownership and tickets as webhooks

chat.assigned, chat.team_assigned, chat.state_changed, ticket.created and chat.resolved, signed like every event.

What the API covers today

Read, route and track from your systems

The public API covers what every channel shares: listing chats with their channel type, assigning people and teams, chat states and workflows, tickets and reports. Sending a LinkedIn message by API is not part of the public surface today; replies go out from the inbox, where the team already works LinkedIn next to everything else. If you need it, tell us.

  • Chats, assignments, tickets, reports: the same partner-safe operations as every channel.
  • Webhooks for assignment, state and ticket changes on LinkedIn conversations.
  • Inbox send for replies, with notes, labels and the audit trail.
Ask us about LinkedIn sending
POST yourapp.com/hooks/lodgestory

                
X-Webhook-Signature · sha256=…
Delivery logLinkedIn · 30 days

Ready to build on LinkedIn?

Create an organisation, enable Developer Access and run your first request against your own workspace today.

Questions, answered

What engineering teams ask before they integrate.

Yes. LinkedIn, messages and your company page inbox, is connected from Settings, Connections, and its conversations arrive in the unified inbox beside every other channel.

Not today. The public API lists LinkedIn chats, manages assignments, states, tickets and reports for them, and webhooks report changes; replies are sent from the inbox. Contact us if you need API sending for LinkedIn.

Routing, team queues, assignment, workflow states, tickets and notes apply to LinkedIn conversations like any channel in the inbox.

message.received for inbound LinkedIn messages, chat.assigned and chat.team_assigned, chat.state_changed and chat.workflow_started, ticket events and chat.resolved, on the same signed envelope.

LinkedIn messaging API | Lodgestory