The Integrations 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 Integrations in its sidebar. You need the Owner or Admin role to see it.
Each 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't on this page: copy the install snippet from Settings → Install & security (see Installing the Chat Messenger on Your Website).
| Group | Integration | What it does |
|---|---|---|
| Channels | Forward 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 the email channel. | |
| Answer messages to your WhatsApp Business number in the inbox. See Connecting WhatsApp to Chat. | ||
| Team and handoff | Slack | Alerts each team in its own Slack channel when a chat starts, needs a person or gets a reply, with one thread per conversation. See Connecting Slack. |
| Freshdesk | Turns a conversation into a Freshdesk ticket so it's followed up in your help desk. See Connecting Freshdesk. | |
| GitHub | Links tickets to the GitHub issues your developers are working on. | |
| Customer data for your AI agent | Shopify | Tells customers where their order is, and can cancel it in a procedure after they confirm. |
| WooCommerce | Tells customers an order's status, items and total, and can cancel it in a procedure. | |
| Stripe | Answers signed-in customers about their plan, renewal date or a failed payment, and can send them a billing portal link. | |
| Marketing and automation | DailyStory | Sends people who chat with you to a DailyStory campaign as leads. |
| Webhooks | Calls your own address when a chat starts, needs a person, gets the customer's details, is closed, reopened or rated. Works with Zapier, Make and n8n. |
Slack and DailyStory use the connection of the messenger's home project, so their cards say Connect in or Manage in followed by the project's name and take you to that project's settings.
| Status | Meaning |
|---|---|
| Off | Not set up yet (Email, WhatsApp, GitHub), or every webhook you added is switched off. |
| Not connected | No account is connected yet (Shopify, WooCommerce, Stripe, Freshdesk, Slack, DailyStory). |
| None yet | You haven't added a webhook. |
| Connected | Set up and working. The card shows what it's connected to and, for most, the date it was connected. |
| {n} active | How many webhooks are switched on, for example 2 active. |
| Needs attention | Connected, but something needs fixing, for example WhatsApp needs reconnecting, or emails arrive but replies can't be sent. The card says what's wrong. |
These connections let your AI agent look up a customer's own orders and billing while it answers. Connecting one adds ready-made actions the AI can use, and actions that change something, like cancelling an order, that only a procedure runs, after the customer confirms. Click the card's Connect button, follow the steps on the page, fill in the fields and click Connect.
| Service | What you enter | What the AI can do |
|---|---|---|
| Shopify | Store address (your myshopify.com address) and an Admin API access token from an app you create under Settings → Apps and sales channels → Develop apps. Give it the read_orders scope, and write_orders if procedures should cancel orders. | Tell 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. |
| WooCommerce | Store address, Consumer key and Consumer secret from WooCommerce → Settings → Advanced → REST API → Add key, with Read permission (or Read/Write to let procedures cancel orders). Your store must use https. | Look up an order's status, items and total. The order's billing email must match the email the customer gives before the AI sees anything. |
| Stripe | A Restricted API key with Read on Customers and Subscriptions (and Write on Customer portal for the billing link), the Metadata field with your user ID (user_id by default), and an optional Return address after managing billing, which adds the billing portal action. | Answer questions about a customer's 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's billing. See identity verification. |
When you click Connect, 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 Connect again.
Disconnect deletes the key and switches the connection's actions off. The actions are kept, so procedures that use them still point at them when you connect again.
GitHub lets your team link a ticket 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.
owner/name or the repository's GitHub address. The first one is picked by default.On a ticket, click GitHub → + Add and type an issue's number, like 482, or paste the full address of any GitHub issue or pull request. It shows on the ticket as a link, like web-app #482. 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.
A webhook sends a JSON POST 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.
| Call it when | Event name |
|---|---|
| A chat starts | conversation.started |
| A chat needs a person | conversation.escalated |
| The customer leaves their details | contact.left |
| A chat is closed | conversation.closed |
| A chat is reopened | conversation.reopened |
| The customer rates the chat | conversation.rated |
Each 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's 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.
Every call has an X-Docent-Signature header, such as t=1731000000,v1=5f2c…. To check it:
t (a Unix time in seconds) and the raw request body, exactly as received.{t}.{body} with the webhook's signing secret, as lower-case hex.v1, and refuse the call if they differ or if t is more than 5 minutes old.Two more headers help: X-Docent-Event names the event, and X-Docent-Delivery stays the same when a call is retried, so you can ignore a repeat. New secret makes a new signing secret; calls signed with the old one stop checking out at once, so update your receiver first.
Send test sends a ping 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.
A 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't retried. Your address must use https and answer within a few seconds; redirects aren't followed.
TipSwitch a webhook off with its On switch to pause it without losing its settings. Remove deletes it.