{"Status":true,"Message":"","Response":{"post":{"postuid":"a8f0c0fd-cd76-430d-82d9-d31339c7b5d2","tenantuid":"d8b744fc-2e70-4089-bb80-dd1d08f6c7b2","projectuid":"fc6490ac-7527-4f49-b06e-46f701280e85","title":"Chat Integrations and Webhooks","slug":"article/chat-integrations-and-webhooks","html":"\u003Cp\u003EThe \u003Cb\u003EIntegrations\u003C/b\u003E page connects a messenger to the places your customers and your team already are: email and WhatsApp, Slack and your help desk, your store and billing system, and your own tools through webhooks. Open a messenger and click \u003Cb\u003EIntegrations\u003C/b\u003E in its sidebar. You need the Owner or Admin role to see it.\u003C/p\u003E\u003Cp\u003EEach integration has a card with a short description, its status and a button to set it up or manage it. Use the search box at the top to find one by name. Connecting your website isn\u0027t on this page: copy the install snippet from \u003Cb\u003ESettings\u003C/b\u003E \u2192 \u003Cb\u003EInstall \u0026amp; security\u003C/b\u003E (see \u003Ca href=\u0022/article/installing-the-chat-messenger-on-your-website\u0022\u003EInstalling the Chat Messenger on Your Website\u003C/a\u003E).\u003C/p\u003E\u003Ch2 id=\u0022the_four_groups\u0022\u003EThe four groups\u003C/h2\u003E\u003Ctable border=\u00221\u0022 style=\u0022border-collapse: collapse; width: 100%;\u0022\u003E\u003Cthead\u003E\u003Ctr\u003E\u003Cth\u003EGroup\u003C/th\u003E\u003Cth\u003EIntegration\u003C/th\u003E\u003Cth\u003EWhat it does\u003C/th\u003E\u003C/tr\u003E\u003C/thead\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Cb\u003EChannels\u003C/b\u003E\u003C/td\u003E\u003Ctd\u003EEmail\u003C/td\u003E\u003Ctd\u003EForward support@, sales@ or any shared address to the messenger. Every email becomes a conversation or ticket, the AI answers first, and replies go back in the same thread. See \u003Ca href=\u0022/article/chat-email-channel\u0022\u003Ethe email channel\u003C/a\u003E.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003C/td\u003E\u003Ctd\u003EWhatsApp\u003C/td\u003E\u003Ctd\u003EAnswer messages to your WhatsApp Business number in the inbox. See \u003Ca href=\u0022/article/connecting-whatsapp-to-chat\u0022\u003EConnecting WhatsApp to Chat\u003C/a\u003E.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Cb\u003ETeam and handoff\u003C/b\u003E\u003C/td\u003E\u003Ctd\u003ESlack\u003C/td\u003E\u003Ctd\u003EAlerts each team in its own Slack channel when a chat starts, needs a person or gets a reply, with one thread per conversation. See \u003Ca href=\u0022/article/connecting-slack\u0022\u003EConnecting Slack\u003C/a\u003E.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003C/td\u003E\u003Ctd\u003EFreshdesk\u003C/td\u003E\u003Ctd\u003ETurns a conversation into a Freshdesk ticket so it\u0027s followed up in your help desk. See \u003Ca href=\u0022/article/connecting-freshdesk\u0022\u003EConnecting Freshdesk\u003C/a\u003E.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003C/td\u003E\u003Ctd\u003EGitHub\u003C/td\u003E\u003Ctd\u003ELinks tickets to the GitHub issues your developers are working on.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Cb\u003ECustomer data for your AI agent\u003C/b\u003E\u003C/td\u003E\u003Ctd\u003EShopify\u003C/td\u003E\u003Ctd\u003ETells customers where their order is, and can cancel it in a procedure after they confirm.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003C/td\u003E\u003Ctd\u003EWooCommerce\u003C/td\u003E\u003Ctd\u003ETells customers an order\u0027s status, items and total, and can cancel it in a procedure.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003C/td\u003E\u003Ctd\u003EStripe\u003C/td\u003E\u003Ctd\u003EAnswers signed-in customers about their plan, renewal date or a failed payment, and can send them a billing portal link.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Cb\u003EMarketing and automation\u003C/b\u003E\u003C/td\u003E\u003Ctd\u003EDailyStory\u003C/td\u003E\u003Ctd\u003ESends people who chat with you to a DailyStory campaign as leads.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003C/td\u003E\u003Ctd\u003EWebhooks\u003C/td\u003E\u003Ctd\u003ECalls your own address when a chat starts, needs a person, gets the customer\u0027s details, is closed, reopened or rated. Works with Zapier, Make and n8n.\u003C/td\u003E\u003C/tr\u003E\u003C/table\u003E\u003Cp\u003ESlack and DailyStory use the connection of the messenger\u0027s home project, so their cards say \u003Cb\u003EConnect in\u003C/b\u003E or \u003Cb\u003EManage in\u003C/b\u003E followed by the project\u0027s name and take you to that project\u0027s settings.\u003C/p\u003E\u003Ch3 id=\u0022what_the_status_means\u0022\u003EWhat the status means\u003C/h3\u003E\u003Ctable border=\u00221\u0022 style=\u0022border-collapse: collapse; width: 100%;\u0022\u003E\u003Cthead\u003E\u003Ctr\u003E\u003Cth\u003EStatus\u003C/th\u003E\u003Cth\u003EMeaning\u003C/th\u003E\u003C/tr\u003E\u003C/thead\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Cb\u003EOff\u003C/b\u003E\u003C/td\u003E\u003Ctd\u003ENot set up yet (Email, WhatsApp, GitHub), or every webhook you added is switched off.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Cb\u003ENot connected\u003C/b\u003E\u003C/td\u003E\u003Ctd\u003ENo account is connected yet (Shopify, WooCommerce, Stripe, Freshdesk, Slack, DailyStory).\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Cb\u003ENone yet\u003C/b\u003E\u003C/td\u003E\u003Ctd\u003EYou haven\u0027t added a webhook.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Cb\u003EConnected\u003C/b\u003E\u003C/td\u003E\u003Ctd\u003ESet up and working. The card shows what it\u0027s connected to and, for most, the date it was connected.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Cb\u003E{n} active\u003C/b\u003E\u003C/td\u003E\u003Ctd\u003EHow many webhooks are switched on, for example \u003Cb\u003E2 active\u003C/b\u003E.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Cb\u003ENeeds attention\u003C/b\u003E\u003C/td\u003E\u003Ctd\u003EConnected, but something needs fixing, for example WhatsApp needs reconnecting, or emails arrive but replies can\u0027t be sent. The card says what\u0027s wrong.\u003C/td\u003E\u003C/tr\u003E\u003C/table\u003E\u003Ch2 id=\u0022shopify_woocommerce_and_stripe\u0022\u003EShopify, WooCommerce and Stripe\u003C/h2\u003E\u003Cp\u003EThese connections let your AI agent look up a customer\u0027s own orders and billing while it answers. Connecting one adds ready-made \u003Ca href=\u0022/article/chat-actions\u0022\u003Eactions\u003C/a\u003E the AI can use, and actions that change something, like cancelling an order, that only a \u003Ca href=\u0022/article/chat-procedures\u0022\u003Eprocedure\u003C/a\u003E runs, after the customer confirms. Click the card\u0027s \u003Cb\u003EConnect\u003C/b\u003E button, follow the steps on the page, fill in the fields and click \u003Cb\u003EConnect\u003C/b\u003E.\u003C/p\u003E\u003Ctable border=\u00221\u0022 style=\u0022border-collapse: collapse; width: 100%;\u0022\u003E\u003Cthead\u003E\u003Ctr\u003E\u003Cth\u003EService\u003C/th\u003E\u003Cth\u003EWhat you enter\u003C/th\u003E\u003Cth\u003EWhat the AI can do\u003C/th\u003E\u003C/tr\u003E\u003C/thead\u003E\u003Ctr\u003E\u003Ctd\u003EShopify\u003C/td\u003E\u003Ctd\u003E\u003Cb\u003EStore address\u003C/b\u003E (your myshopify.com address) and an \u003Cb\u003EAdmin API access token\u003C/b\u003E from an app you create under \u003Cb\u003ESettings \u2192 Apps and sales channels \u2192 Develop apps\u003C/b\u003E. Give it the \u003Ccode\u003Eread_orders\u003C/code\u003E scope, and \u003Ccode\u003Ewrite_orders\u003C/code\u003E if procedures should cancel orders.\u003C/td\u003E\u003Ctd\u003ETell customers their payment and shipping status, items and tracking links. It only finds an order when the customer gives both the order number and the email it was placed with.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003EWooCommerce\u003C/td\u003E\u003Ctd\u003E\u003Cb\u003EStore address\u003C/b\u003E, \u003Cb\u003EConsumer key\u003C/b\u003E and \u003Cb\u003EConsumer secret\u003C/b\u003E from \u003Cb\u003EWooCommerce \u2192 Settings \u2192 Advanced \u2192 REST API\u003C/b\u003E \u2192 \u003Cb\u003EAdd key\u003C/b\u003E, with \u003Cb\u003ERead\u003C/b\u003E permission (or \u003Cb\u003ERead/Write\u003C/b\u003E to let procedures cancel orders). Your store must use https.\u003C/td\u003E\u003Ctd\u003ELook up an order\u0027s status, items and total. The order\u0027s billing email must match the email the customer gives before the AI sees anything.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003EStripe\u003C/td\u003E\u003Ctd\u003EA \u003Cb\u003ERestricted API key\u003C/b\u003E with \u003Cb\u003ERead\u003C/b\u003E on Customers and Subscriptions (and \u003Cb\u003EWrite\u003C/b\u003E on Customer portal for the billing link), the \u003Cb\u003EMetadata field with your user ID\u003C/b\u003E (\u003Ccode\u003Euser_id\u003C/code\u003E by default), and an optional \u003Cb\u003EReturn address after managing billing\u003C/b\u003E, which adds the billing portal action.\u003C/td\u003E\u003Ctd\u003EAnswer questions about a customer\u0027s plan, price, renewal date or a failed payment. It only answers for a signed-in customer whose user ID your website verifies, so nobody can see someone else\u0027s billing. See \u003Ca href=\u0022/article/chat-identity-verification\u0022\u003Eidentity verification\u003C/a\u003E.\u003C/td\u003E\u003C/tr\u003E\u003C/table\u003E\u003Cp\u003EWhen you click \u003Cb\u003EConnect\u003C/b\u003E, Docent checks the details with the service and then lists the actions it added. Keys are stored encrypted and never shown again; to change one, use \u003Cb\u003EConnect again\u003C/b\u003E.\u003C/p\u003E\u003Cp\u003E\u003Cb\u003EDisconnect\u003C/b\u003E deletes the key and switches the connection\u0027s actions off. The actions are kept, so procedures that use them still point at them when you connect again.\u003C/p\u003E\u003Ch2 id=\u0022github\u0022\u003EGitHub\u003C/h2\u003E\u003Cp\u003EGitHub lets your team link a \u003Ca href=\u0022/article/working-with-tickets\u0022\u003Eticket\u003C/a\u003E to the issues your developers are working on. It only stores links: nothing is read from GitHub and no key is needed. The links open GitHub, so private repositories work for anyone who has access to them there.\u003C/p\u003E\u003Col\u003E\u003Cli\u003EOn the GitHub card, click \u003Cb\u003ESet up\u003C/b\u003E.\u003C/li\u003E\u003Cli\u003EUnder \u003Cb\u003ERepositories\u003C/b\u003E, enter the repositories your team files issues in, one per line, as \u003Ccode\u003Eowner/name\u003C/code\u003E or the repository\u0027s GitHub address. The first one is picked by default.\u003C/li\u003E\u003Cli\u003EClick \u003Cb\u003ESave\u003C/b\u003E.\u003C/li\u003E\u003C/ol\u003E\u003Cp\u003EOn a ticket, click \u003Cb\u003EGitHub\u003C/b\u003E \u2192 \u003Cb\u003E\u002B Add\u003C/b\u003E and type an issue\u0027s number, like 482, or paste the full address of any GitHub issue or pull request. It shows on the ticket as a link, like \u003Cb\u003Eweb-app #482\u003C/b\u003E. With more than one repository, pick the right one beside the number; a pasted address names its own. To switch GitHub off, clear the list and save. Issues already linked to tickets stay.\u003C/p\u003E\u003Ch2 id=\u0022webhooks\u0022\u003EWebhooks\u003C/h2\u003E\u003Cp\u003EA webhook sends a JSON \u003Ccode\u003EPOST\u003C/code\u003E to your address when something happens in a conversation, so tools such as Zapier, Make, n8n or your own systems can act on it. A messenger can have up to 5 webhooks. Test chats never send anything.\u003C/p\u003E\u003Col\u003E\u003Cli\u003EOn the Webhooks card, click \u003Cb\u003EAdd webhook\u003C/b\u003E (or \u003Cb\u003EManage\u003C/b\u003E, then \u003Cb\u003EAdd a webhook\u003C/b\u003E).\u003C/li\u003E\u003Cli\u003EEnter a \u003Cb\u003EName\u003C/b\u003E and the \u003Cb\u003EAddress (https)\u003C/b\u003E to call.\u003C/li\u003E\u003Cli\u003EUnder \u003Cb\u003ECall it when\u003C/b\u003E, tick the events you want.\u003C/li\u003E\u003Cli\u003ELeave \u003Cb\u003EOn\u003C/b\u003E switched on and click \u003Cb\u003EAdd webhook\u003C/b\u003E. The webhook\u0027s signing secret then appears, with \u003Cb\u003ECopy\u003C/b\u003E.\u003C/li\u003E\u003C/ol\u003E\u003Ctable border=\u00221\u0022 style=\u0022border-collapse: collapse; width: 100%;\u0022\u003E\u003Cthead\u003E\u003Ctr\u003E\u003Cth\u003ECall it when\u003C/th\u003E\u003Cth\u003EEvent name\u003C/th\u003E\u003C/tr\u003E\u003C/thead\u003E\u003Ctr\u003E\u003Ctd\u003EA chat starts\u003C/td\u003E\u003Ctd\u003E\u003Ccode\u003Econversation.started\u003C/code\u003E\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003EA chat needs a person\u003C/td\u003E\u003Ctd\u003E\u003Ccode\u003Econversation.escalated\u003C/code\u003E\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003EThe customer leaves their details\u003C/td\u003E\u003Ctd\u003E\u003Ccode\u003Econtact.left\u003C/code\u003E\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003EA chat is closed\u003C/td\u003E\u003Ctd\u003E\u003Ccode\u003Econversation.closed\u003C/code\u003E\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003EA chat is reopened\u003C/td\u003E\u003Ctd\u003E\u003Ccode\u003Econversation.reopened\u003C/code\u003E\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003EThe customer rates the chat\u003C/td\u003E\u003Ctd\u003E\u003Ccode\u003Econversation.rated\u003C/code\u003E\u003C/td\u003E\u003C/tr\u003E\u003C/table\u003E\u003Cp\u003EEach call includes the event and when it happened, the messenger, the conversation (status, who has it, subject, channel, start page, language, team and a link to it in the inbox), the customer (name, email, phone, country, and their user ID when it\u0027s verified), any follow-up details collected, the rating and comment for a rating, and the latest messages the customer saw. Internal notes are never included.\u003C/p\u003E\u003Ch3 id=\u0022checking_a_call_came_from_docent\u0022\u003EChecking a call came from Docent\u003C/h3\u003E\u003Cp\u003EEvery call has an \u003Ccode\u003EX-Docent-Signature\u003C/code\u003E header, such as \u003Ccode\u003Et=1731000000,v1=5f2c\u2026\u003C/code\u003E. To check it:\u003C/p\u003E\u003Col\u003E\u003Cli\u003ETake \u003Ccode\u003Et\u003C/code\u003E (a Unix time in seconds) and the raw request body, exactly as received.\u003C/li\u003E\u003Cli\u003ECompute HMAC-SHA256 of \u003Ccode\u003E{t}.{body}\u003C/code\u003E with the webhook\u0027s signing secret, as lower-case hex.\u003C/li\u003E\u003Cli\u003ECompare it with \u003Ccode\u003Ev1\u003C/code\u003E, and refuse the call if they differ or if \u003Ccode\u003Et\u003C/code\u003E is more than 5 minutes old.\u003C/li\u003E\u003C/ol\u003E\u003Cdiv class=\u0022code_wrapper\u0022\u003E\u003Cdiv class=\u0022code\u0022 data-language=\u0022javascript\u0022\u003Econst crypto = require(\u0026#39;crypto\u0026#39;);\n\nfunction isFromDocent(rawBody, signatureHeader, secret) {\n  const parts = Object.fromEntries(signatureHeader.split(\u0026#39;,\u0026#39;).map(p =\u0026gt; p.split(\u0026#39;=\u0026#39;)));\n  const expected = crypto.createHmac(\u0026#39;sha256\u0026#39;, secret)\n    .update(\u0060${parts.t}.${rawBody}\u0060)\n    .digest(\u0026#39;hex\u0026#39;);\n  const fresh = Math.abs(Date.now() / 1000 - Number(parts.t)) \u0026lt; 300;\n  return fresh \u0026amp;\u0026amp; crypto.timingSafeEqual(Buffer.from(expected), Buffer.from(parts.v1 || \u0026#39;\u0026#39;));\n}\u003C/div\u003E\u003C/div\u003E\u003Cp\u003ETwo more headers help: \u003Ccode\u003EX-Docent-Event\u003C/code\u003E names the event, and \u003Ccode\u003EX-Docent-Delivery\u003C/code\u003E stays the same when a call is retried, so you can ignore a repeat. \u003Cb\u003ENew secret\u003C/b\u003E makes a new signing secret; calls signed with the old one stop checking out at once, so update your receiver first.\u003C/p\u003E\u003Ch3 id=\u0022testing_and_delivery_results\u0022\u003ETesting and delivery results\u003C/h3\u003E\u003Cp\u003E\u003Cb\u003ESend test\u003C/b\u003E sends a \u003Ccode\u003Eping\u003C/code\u003E event with a sample conversation to your address. The result appears under the webhook after a few seconds. Each webhook shows its last call: the event delivered with the HTTP status and time, or the event that failed, why, and after how many tries.\u003C/p\u003E\u003Cp\u003EA call that fails with a network error, a timeout, HTTP 429 or a 5xx error is tried again, up to 4 tries in all, about 30 seconds, 2 minutes and 10 minutes apart. Other error responses aren\u0027t retried. Your address must use https and answer within a few seconds; redirects aren\u0027t followed.\u003C/p\u003E\u003Ccite class=\u0022recommended\u0022\u003E\u003Cspan class=\u0022title\u0022\u003ETip\u003C/span\u003E\u003Cp\u003ESwitch a webhook off with its \u003Cb\u003EOn\u003C/b\u003E switch to pause it without losing its settings. \u003Cb\u003ERemove\u003C/b\u003E deletes it.\u003C/p\u003E\u003C/cite\u003E","publish_status":0,"post_type":"Article","author":{},"featured_image_updating":false,"meta_description":"Learn how to connect and manage chat integrations and webhooks to link your messenger with email, WhatsApp, Slack, help desks, stores, billing, and custom tools.","display_toc":true,"has_workingcopy":false,"allow_indexing":true,"total_views":0,"date_published":"2026-11-15T17:38:32.553","date_updated":"2026-11-15T17:38:33.333","date_created":"2026-11-15T14:17:09.84"}}}