Set up and use Custom Integrations in Demodesk
Custom Integrations let your team connect external tools to Demodesk and control which API endpoints the AI is allowed to use. This makes it possible to connect systems such as HubSpot, Slack, Intercom, GitLab, Gmail, and more. Martin’s launch note confirms that Custom APIs can be used in chat and with agents, and that the API key must still be added in Settings. Based on the screenshots you shared, each connection also includes configurable endpoint permissions so admins can define what the AI is allowed to do.
Where to find Custom Intregations
To add or manage a Custom Intregation in Demodesk, go to:
This is where admins can create new API connections, manage existing ones, add API keys, and define endpoint permissions.
How to add a Custom Intregations
To create a new Custom API connection:
Open Settings
Go to Integrations
Select Connections
Open Custom APIs
Click to add a new Custom API or open an existing one
Enter the following details:
Name
Base URL
API key
Turn the integration on to be used by the AI Analyst
Add the allowed endpoint permissions
Optionally add Instructions for AI
Click Save
What you can connect
You can use Custom APIs to connect Demodesk to external systems such as:
HubSpot
Slack
GitLab
Gmail
Intercom
Amplemarket
How Custom APIs work
A Custom API connection is more than just a saved API key. It also defines how the AI can use that API.
Each connection includes:
A Name to identify the integration
A Base URL for the external service
An API key
An Enabled toggle to make the integration available for use by the AI Analyst
One or more Endpoint permissions
Optional Instructions for AI
This setup gives admins control over which parts of an external API the AI can access.
Configure endpoint permissions
Endpoint permissions define which requests the AI is allowed to make.
For each permission, you can configure:
Whether the permission is enabled
The allowed HTTP method(s), such as GET or POST
A URL pattern, such as /* or /crm/v3/objects/*/search
An optional comment to describe the purpose of the permission
For example, one permission allows GET requests to /*, while another allows POST requests.
This means admins can restrict access to exactly the endpoints needed for the use case, rather than exposing the entire API without controls.
Add instructions for AI
You can also add optional instructions to guide how the AI should use the API.
This can be helpful if you want to clarify which endpoints are intended for certain actions, provide context about the connected system, or steer the AI toward safe and expected usage.
Important security note
Every user in the company can use every configured Custom API. Because of this, admins should be careful about which API keys they add and how much access those keys provide.
As a best practice:
only allow the endpoints the AI actually needs
only allow the required HTTP methods
use API keys with limited permissions whenever possible
avoid using overly broad or highly privileged API keys
Ideally, the API key should only be as powerful as the intended use case requires.