Slack

The Slack channel mirrors Lane.Chat conversations into a Slack workspace, so your team can read and reply to customer chats without leaving Slack. Rich messages are translated to Slack Block Kit.

How it works

1. Install the Lane.Chat Slack app into your workspace via OAuth (a one-click install flow from the dashboard).
2. Conversations are posted into Slack with chat.postMessage; edits and deletions use chat.update / chat.delete.
3. Agent replies and interactive actions in Slack are delivered back to Lane.Chat through the Events and Actions endpoints and routed to the visitor.

Installations are stored per workspace; bot tokens and signing secrets are held encrypted.

OAuth and endpoints

GET  https://api.lane.chat/api/v1/slack/install    # start OAuth v2 install
GET  https://api.lane.chat/api/v1/slack/callback   # OAuth redirect target
POST https://api.lane.chat/api/v1/slack/events     # Slack Events API
POST https://api.lane.chat/api/v1/slack/actions    # interactive actions (buttons, etc.)
GET  https://api.lane.chat/api/v1/slack/media/{fileId}  # media proxy

Inbound Slack requests are verified with Slack's v0 request signature (HMAC-SHA256 over the timestamp and raw body using the signing secret).

Block Kit translation

Outbound rich messages are converted to Block Kit:

• Cards and buttons become section + actions blocks with interactive buttons.
• Carousels render as a series of card blocks.
• Markdown maps to mrkdwn sections.
• Forms and unsupported types fall back to their plain-text representation.

Button clicks in Slack come back through the Actions endpoint and drive the same Flow logic as any other channel.