Connect VK to EnkaChat

Prerequisites

• A workspace with the channels:manage permission and the omnichannel plan feature
• Admin or member rights on the VK community you want to connect
• Community messages and bot capabilities enabled on the community
• A publicly reachable HTTPS origin with a CA-signed certificate for the Callback API server

Before you start

You need a workspace with the channels:manage permission and the omnichannel plan feature, plus admin or member rights on the VK community. The VK Callback API only delivers events to a publicly reachable HTTPS URL with a CA-signed certificate, so have a deployed origin or a public HTTPS tunnel ready.

Enable community messages and bot capabilities

In the VK community, open Management -> Communications and enable community messages, then enable The capabilities of bots in the same section. Community members can now message the community.

Create a community access token and find the community ID

Open Management -> Working with API and create a key for the community access token; VK ID two-factor authentication may be required the first time. The numeric community ID for group_id is shown in the same section.

vk1.a.<your-token>

Copy the Callback API confirmation code and optional secret key

Open Management -> Working with API -> Callback API. Copy the confirmation string for confirmation_code and, optionally, set a Secret key. When a secret key is set, VK echoes it as the top-level secret field on every event so EnkaChat can verify the payload in constant time.

<confirmation-string>

Connect VK in EnkaChat

In the admin panel, open Integrations at http://app.enkachat.localhost and find the VK card. Click Connect and fill in the Group token, Group ID, Confirmation code, and an optional Secret key. EnkaChat shows the webhook URL and a one-time connection token; copy the token before closing the dialog.

http://api.enkachat.localhost/webhooks/vk/<connection-token>

Configure the Callback API in VK

Back in VK, open Management -> Working with API -> Callback API and add a server address: the webhook URL EnkaChat gave you. Set the API version to 5.199 and select the incoming messages event. VK sends a confirmation event, EnkaChat replies with your stored confirmation code, and VK marks the server confirmed.

5.199

Verify the connection

Run the Health check; it calls VK's groups.getById with the group ID and token. The status badge moves from pending to active once the first verified event arrives. Send a test message to the community from a VK account; it lands as a channel session in the Chats inbox, where agents reply alongside website chat, Telegram, and WhatsApp.

Behavior and limits

Outbound replies carry the text body only; outbound attachments are dropped. Inbound photo, document, and audio attachments are downloaded up to the 10 MiB cap, while video attachments are skipped. Only direct community messages are handled, not group-chat or peer conversations.

• Status lifecycle: pending, active, error, disabled
• Disabling pauses inbound processing; deleting removes the connection
• Duplicate deliveries are dropped via the channel_events unique triple; VK retries arrive with the X-Retry-Counter header

Add a VK contact button to the site widget

In the site widget's Channels settings (Settings -> Widget -> Channels) you can add a VK profile link button. Once the VK integration has an active connection, GET /widget/config marks VK as connected and the widget hides that contact link, because messages now land in the shared inbox.

FAQ