VK

Choose Personal profile for private account conversations. If customers message a community, connect Community so operators reply on its behalf.

Before you connect

• Personal profile: access to the correct VK account and permission approval.
• Community: administrator access and community messages enabled.

Open the correct workspace in Chatva → Channels → the channel card → Connect. On first connection, use Next to go through the introductory steps. In the mobile app, the same guide is available during onboarding and under Channels.

Choose your connection method

Personal profile

1. 1

   Choose Personal profile → Sign in with VK

   Sign in to the intended account and review the requested permissions. Approve access so Chatva can receive messages and send replies.

2. 2

   On web, copy the address after sign-in

   After approval, the browser may show a blank oauth.vk.com/blank.html page. Copy its entire address, including the part after #, into Page address after sign-in → Connect.

3. 3

   In the app, finish embedded sign-in

   Chatva normally captures sign-in automatically. If the window fails, choose Paste the link manually and use the complete page address.

Community: automatic connection

First enable messages in the VK community settings. Choose Community in Chatva. If VK ID sign-in is available, enter the community link or ID, press Connect on web / Connect through VK ID in the app, and approve access. Credentials, confirmation and webhook are configured automatically.

Community: manual connection

Enable messages and get a VK token

1. 1

   Open a community you administer

   Choose your community in VK Communities. Open Management → Messages, enable community messages and save. VK message settings help.

Enlarge

VK: Management on the community page. Screenshot from official help, in Russian.

Source: VK · Ключ доступа сообщества ↗

100%

2. 2

   Create a messaging token

   In your VK community, open Management → Additional → API usage → Access tokens → Create token. Grant access to community messages, create the token and complete VK’s verification prompt. VK instructions.

3. 3

   Copy the complete token

   In Access tokens, press Show for the created token and copy the full value. This must be a community token, not a personal-profile token. Token location.

Enlarge

VK: API usage → Access tokens → Create token. Credential hidden; you do not need every permission shown in the example.

Source: VK · Получение ключа ↗

100%

Configure Callback API in VK

1. 1

   Add a Callback API server

   In API usage, open Callback API → Add server. Name it Chatva and copy the webhook URL from the correct Chatva workspace’s form into Address. VK navigation.

2. 2

   Copy the confirmation string and ID

   Below Address, find the string the server must return and copy it into Chatva’s Confirmation string field. The sample request’s group_id is the numeric community ID. Use your server’s values, not the screenshot’s examples. VK field reference.

3. 3

   Set a secret and save the connection first

   Set a random value in Secret key. Enter exactly the same value in Chatva together with the ID, access token and confirmation string. Save the fields in Chatva first, then return to Callback API settings to confirm the server address.

Enlarge

Crop from VK’s official example: address, confirmation string and secret. Secret values hidden; the current dashboard may look different.

Source: VK · Подключение Callback API ↗

100%

After confirmation, open Event types and enable incoming messages (message_new). If messages do not arrive, check the server’s Requests tab. VK events and diagnostics.

Test an incoming message and a reply

1. 1

   Write from a different account

   Send “Connection test” to the connected profile or community messages. Use a different account to test an incoming customer message.

2. 2

   Find the conversation in Chatva

   Open the correct workspace’s Inbox and check the channel and sender. If an assignee or status filter is active, switch to all conversations.

3. 3

   Reply from the inbox

   Send “Message received” and confirm on the customer’s side that it arrived from the correct number, bot or page. Connection status alone does not confirm two-way delivery.

What reaches the inbox

A community connection receives private messages, not post comments. Personal profiles provide account conversations; recent history may load partially. Always verify using a new message.

Troubleshooting

Official guides and next steps