Integrations and API

Bitrix24 integration

Bitrix24 integration The integration links conversations in Kulpunai with deals and contacts in Bitrix24. What it gives you - Contacts from Kulpunai appear in the CRM; - Deals are created from requests; - Conversations are attached to the customer's card in Bitrix24; - The AI Agent can fill deal and contact fields from the conversation. Connecting 1. Open Settings → Integrations. 2. Find Bitrix24 and start the connection. 3. Authorise on your Bitrix24 portal and grant the requested permissions. This is a plan add-on — see Settings → Billing. Fields for the AI Agent The integration settings include the fields the assistant is allowed to fill during a conversation. Add a description to each field explaining to the AI what to extract. For a "delivery city" field, for instance, "the city the customer asks the order to be delivered to" works well. The more precise the description, the fewer mistakes. Start with two or three key fields and expand once you have checked the results. Disconnecting Removing the integration stops contact and conversation syncing. Data already sent to Bitrix24 stays in the CRM. Other integrations Settings → Integrations also offers Slack, Linear, Notion, Dialogflow, Google Translate and Shopify. They all connect the same way: find the app in the list and authorise.

Webhooks

Webhooks A webhook sends an HTTP request to your address when something happens in Kulpunai. It is how the platform is wired into your own systems. Setting one up 1. Open Settings → Integrations → Webhooks. 2. Add a webhook. 3. Enter: - URL — where requests should go; - Events — what to react to. Events - conversation_created — a conversation was created; - conversation_updated — a conversation changed; - conversation_status_changed — the status changed; - message_created — a new message; - message_updated — a message was edited; - webwidget_triggered — a visitor opened the website widget. Payload format The request arrives as a POST with a JSON body: { "event": "message_created", "id": 123, "content": "Hello", "conversation": { }, "sender": { }, "account": { } } The fields present depend on the event. Uses - Pushing leads into your own CRM or accounting system; - Notifications in a corporate chat; - Recording requests in an external database; - Triggering your own processing. Recommendations - Use an HTTPS endpoint. - Respond quickly: a slow response leads to retries. - Handle repeats — the same event can arrive twice. - Test against a scratch endpoint before pointing a production system at it.

Dashboard apps

Dashboard apps A dashboard app embeds an external page directly into the conversation view, so agents see what they need without switching systems. Setting one up 1. Open Settings → Integrations → Dashboard Apps. 2. Configure an app. 3. Enter a name and the page URL. The app appears in the panel beside the conversation. Receiving conversation context The embedded page receives conversation and contact data through window messages: window.addEventListener("message", (event) => { const data = JSON.parse(event.data); // data holds the conversation and contact details }); You can request fresh data yourself: window.parent.postMessage( 'kulpunai-dashboard-app:fetch-info', '*' ); Uses - An order card from your own system; - A customer's purchase history; - Delivery status; - Data from an accounting system. Recommendations - The page has to be served over HTTPS. - Design a narrow layout: it is shown in a side panel. - Do not ask agents to sign in separately — use the contact identifier from the context.

API and access token

API and access token Calls to the Kulpunai API need a personal access token. Finding the token 1. Click your avatar in the sidebar. 2. Choose Profile Settings. 3. Find the access token section. 4. Copy the value. Using it The token goes in the api_access_token header: curl -H "api_access_token: YOUR_TOKEN" https://online.kulpunai.com/api/v1/accounts/1/conversations Your account ID is visible in the dashboard's address bar. What the API can do - Read and create conversations; - Send messages; - Manage contacts; - Read reporting data. The API channel For your own integrations it is convenient to create an API inbox: messages are pushed into it by request, and agents reply in the normal interface. Create it under Settings → Inboxes. Security - The token grants full access to your account — treat it like a password. - Never put it in website code or a public repository: it belongs on your server only. - Keep it in environment variables. - If you suspect it leaked, regenerate the token and update every integration — the old one stops working immediately.