Repository navigation
Let the support chat set up connectors and tell customers about handoffs - #1623
Merged
Merged
Conversation
The desk's AI assistant can call a custom Libredesk tool that installs a catalog connector for the signed-in customer, or fills their empty one, and returns a one-time link for what is still missing. Keys the customer pasted in the chat are used, as for Telegram, only when their own messages contain them, after the setup check passes. Libredesk drops the assistant's text on a handoff, so the customer now gets a notice that a person replies here.
helpcodeai
enabled auto-merge (squash)
November 10, 2026 14:52
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Two additions to the support desk integration (Cloud only,
ee/support):POST /api/support/desk-tools/connector, called by a custom AI tool in Libredesk (ai_tools, headerX-Desk-Tool-Key= HMAC ofLIBREDESK_WEBHOOK_SECRET, no new variable).X-Libredesk-Contact-External-Id=<host>:<userId>from the widget JWT we sign), checked again against the conversation, then email verified, exactly one workspace, ADMIN/EDITOR. Same trust anchor as the Telegram auto-setup (Set up Telegram from a bot token posted in the support chat #1583).ConnectorSetupService.createLink).verifyCredentials) runs first and a refused key is not stored. Answers never echo values (provider messages are scrubbed).updateEnvVarspath). A pasted Telegram token stays with the message webhook.CONNECTOR_INSTALLED_VIA_SUPPORT_CHAT(via: desk_assistant), product event, and with pasted values the email to the user and workspace admins. At most 5 a day per workspace.LIBREDESK_AI_ASSISTANT_USER_ID) posts its private note in a live chat, the customer gets a short notice in the triage language (8 languages, English fallback) that a person replies here, once per conversation in 6 hours.Small AGPL change:
AdaptersModuleexportsConnectorSetupService, which gains a publicconnectorStatus().Deployment modes
Self-hosted: the support module is not loaded (no
SUPPORT_CHAT_*/LIBREDESK_*), nothing changes. Cloud: the endpoint answers 404 untilLIBREDESK_*is set (it is), and does nothing until the tool is created in Libredesk.Tests
In
packages/backend:npx jest --maxWorkers=4 src/ee/support src/adapters/connector-setup: 137 passednpx tsc --noEmit -p tsconfig.json: cleannpx eslint src/ee/support src/adapters/connector-setup.service.ts src/adapters/adapters.module.ts: clean