Setting up an HTTP Integration

Last updated: February 25, 2026

An HTTP Integration connects Engaige to any external system: your order management platform, CRM, logistics provider, or any REST API. Once an Integration is set up, you can define HTTP Actions on top of it that your AI Agent can call during conversations.


Integration Group vs. Integration

Engaige uses two layers to represent a connection:

  • Integration Group: represents the system (e.g. "Order Management", "My CRM"). Actions are defined at the Integration Group level, so they work regardless of which environment the agent uses.

  • Integration: represents a specific instance of that system (e.g. production and staging). An Integration Group can contain multiple Integrations.

Each AI Agent can use one Integration per Integration Group, but can connect to multiple Integration Groups at the same time.


Step 1 — Create the Integration

  1. Go to Settings → Integrations.

  2. Click + HTTP Integration in the top-right corner.

  3. Give the integration a descriptive name (e.g. "Order Management — Production").

  4. Enter the base URL of the API (e.g. https://api.mystore.com). All Action endpoint paths will be appended to this base.

  5. Select the authentication method required by the API and enter the credentials.

  6. Save. Engaige automatically places this Integration inside an Integration Group with the same name. You can rename the group from the Integration Group page if needed.


Step 2 — Assign the Integration to your Agent

An agent can only call Actions from an Integration Group it's explicitly connected to.

  1. Go to AI Agents and open the agent you want to configure.

  2. Navigate to the External Systems tab.

  3. Click + and select the Integration from the dropdown.

  4. Save the agent.

If you have multiple Integrations in the same group (e.g. production and staging), assign the appropriate one to each agent. If no Integration is assigned, the agent defaults to the first one created in that group.


Next step — Create your first Action

With the Integration in place, you can now define the specific API calls your agent can make. See 📄 How to set up an HTTP Actionto configure endpoints, dynamic parameters, and testing.