Integrations
Connect BLEUM to your existing tools so your AI agent can look up data, create records, and take action during calls.
What are Integrations?
Integrations let your AI agent talk to other software during a call. For example, the AI can look up a customer in your CRM, check an account balance in your billing system, or create a support ticket — all while on the phone with the caller.
BLEUM comes with pre-built integrations for popular tools and also lets you build custom integrations to connect to any system with a REST API.
What You Can Do Here
Build Custom Integrations
Connect to any REST API by configuring the URL, headers, authentication, and response mapping.
Use Pre-Built Connectors
Quick-start integrations for Zendesk, scheduling, and other common tools.
Test Connections
Run test calls with sample data to verify your integration works before using it in live procedures.
Map Response Data
Extract specific fields from API responses and store them as variables for use in your flows.
Building a Custom Integration
Click "New Integration" and give it a descriptive name and slug (like "lookup-customer").
Set the HTTP method (GET, POST, etc.), URL, and any headers. Use {{variable}} placeholders for dynamic values.
Choose the auth type — Bearer token, API key, Basic auth, or custom headers — and enter your credentials.
Tell BLEUM which fields to extract from the API response. These become variables you can use in your flow.
Use the test panel to run the integration with sample data. Verify the response mapping works correctly, then save.
Using Integrations in Flows
Once an integration is saved, you can use it in Flow Builder by adding an Action node. In the Action node configuration:
- Select your integration from the dropdown
- Map flow variables to the integration's input parameters
- Choose where to store the response data
Authentication Types
| Type | Use Case |
|---|---|
| Bearer Token | Most REST APIs, including modern SaaS platforms. |
| API Key | Simple header-based authentication. Common for internal APIs. |
| Basic Auth | Username and password combination. Used by some legacy systems. |
| Custom Header | For APIs that use non-standard authentication headers. |
Common Questions
Yes. API credentials are encrypted and stored in your organization's isolated database. They are never shared across organizations or exposed in logs.
If an API call fails, the AI will continue with the flow. You can configure fallback behavior in your Condition nodes to handle cases where expected data is not available.