> For the complete documentation index, see [llms.txt](https://docs.nlx.ai/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nlx.ai/platform/nlx-platform-guide/integrations/overview.md).

# Overview

### What are Integrations?

Integrations in agentic CX designer are how you connect your conversational applications to the external systems, models, and services they depend on. Whether you need to fetch data from your internal APIs, use a specific Large Language Model, or configure third-party tooling, integrations make those capabilities available across your workspace for use with any of your AI apps.

Once an integration is added, its related resources become instantly available for use in flows, agent tool calls, testing, and deployment. 

To simplify, we can think of integrations in three primary categories, each serving a different purpose in your conversational AI stack:

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><i class="fa-plug">:plug:</i></td><td><strong>Managed integrations</strong></td><td>Prebuilt integrations with providers that agentic CX designer supports out of the box</td></tr><tr><td><i class="fa-wrench">:wrench:</i></td><td><strong>Custom integrations</strong></td><td>For connecting agentic CX desigenr to your own systems. Think internal APIs, custom services, or bespoke endpoints not covered by managed integrations</td></tr></tbody></table>

#### Managed integrations

These are prebuilt connectors for services. Adding them typically involves authenticating with the provider and enabling agentic CX designer to use the service.

They can be used in two ways in an agentic CX designer flow:

1. Assigned to an agentic node as a tool
2. Used in the Data request node that deterministically triggers an API call

To access these types of integrations, select *Resources* in your workspace menu and choose the *Integrations.*

#### Custom integrations

Custom integrations are user-defined API integrations that let your application communicate with your own services or bespoke endpoints.&#x20;

They can be used in two ways in an agentic CX designer flow:

1. Assigned to an agentic node as a tool
2. Used in the Data request node that deterministically triggers an API call

To access this type of integration, select *Resources* in your workspace menu and choose the *Data requests.*

### How integrations work

When you complete the one-time setup of any integration:

* It becomes available to all applications and flows in your workspace
* Flows can call it via agent tools or Data request nodes
* Permissions, settings, and auth tokens stay centrally managed
* Updates apply automatically everywhere the integration is used


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nlx.ai/platform/nlx-platform-guide/integrations/overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.