Connectors in Elastic Agent Builder
The connectors library is hidden until you turn on the agentBuilder:experimentalFeatures advanced setting in Kibana.
The Elastic Agent Builder connectors library lets you configure action-based connectors that give agents access to external systems, such as messaging services, cloud functions, and third-party APIs.
Elastic Agent Builder connectors leverage the underlying Kibana Stack connectors framework to securely store credentials and manage integrations. However, they are distinct from AI connectors, which are used exclusively to configure external LLM providers.
Connectors are managed at the deployment level from Manage components > Connectors. They are not assigned per agent. Individual connector types in the catalog may be marked Technical Preview.
Unlike standalone tools, Elastic Agent Builder connectors do not require manual assignment to agents. Kibana makes connector capabilities natively available during conversations through a dynamic schema-attachment model.
When an agent needs to interact with an external system, it automatically reads the schemas of your configured connectors. It then uses a built-in system tool (platform.core.execute_connector_sub_action) to independently format API payloads and run specific sub-actions (for example, looking up a Slack channel ID or searching AlienVault OTX for threat intelligence) without any manual tool mapping.
To register a new connector:
- In the left sidebar, select Manage components > Connectors.
- Select the mosaic to add a connector.
- Choose a connector type from the catalog.
- Provide the required configuration.
- Save the connector.
The configured connector appears in the library and is immediately available for your agents to use dynamically.
When an agent needs access to an OAuth connector, the chat pauses and displays an authorization prompt. Select Authorize to open the provider's sign-in flow in a new browser tab. After authorization succeeds, return to the chat, where the agent retries the connector call and continues. Select Deny to cancel the call.
If authorization fails or the provider does not return you to Kibana, close the provider tab and select Deny in the chat. Correct the connector or OAuth configuration, then retry your request. To learn more about this prompt, refer to Authorize a connector.