What are Integrations?
Integrations allow your phone agents to connect with external systems during conversations. Instead of manually programming each API call, you define reusable tools that your agents can use when needed. For example, a support agent can:- Look up customer information in your CRM
- Create tickets in your management system
- Process returns in your payment platform
- Check inventory in your database
Integrations are optional. You can create agents that only converse without performing external actions. Use them when you need your agent to do something besides talking.
Common Use Cases
Integrations elevate your agents’ capabilities across multiple cases: Customer Service- Look up customer information in CRM
- Check order status
- Create support tickets
- Check product availability
- Verify prices and discounts
- Process orders
- Check account balances
- Verify transactions
- Process refunds
Key Concepts
Tools
A tool is a specific action your agent can perform. Examples:search_customer- Searches for a customer by phone or emailcreate_ticket- Creates a support ticketcheck_inventory- Verifies product availabilityprocess_refund- Initiates a return
- Name: Unique identifier (e.g.,
search_customer) - Description: Explains when to use it
- Parameters: Information it needs (e.g., phone number, email)
Integrations
An integration is a container that groups related tools and manages the connection with an external system. For example, a “Zendesk” integration could include:search_customercreate_ticketupdate_ticketcheck_ticket_status
How Integrations Work During a Call
When a user is on a call with your agent, it can use assigned tools to perform actions in real-time:1
The user requests something
The user makes a request during the conversation (e.g., “What’s the status of my order 12345?”)
2
The agent identifies the need
The agent recognizes it needs to use a tool to respond (e.g.,
check_order)3
The agent calls the tool
The agent executes the tool with the necessary parameters (e.g.,
order_id=12345)4
The external system responds
The integration queries the external system and returns the data to the agent
5
The agent responds to the user
The agent uses the received information to give a clear response (e.g., “Your order is on its way and should arrive tomorrow”)
Types of Integrations
Diga supports two types of integrations:HTTP
You create tools manually by defining endpoints, parameters, and authentication. It’s the most flexible option.
MCP (Model Context Protocol)
Tools are automatically synced from the server. The provider manages updates.
User Confirmation
For sensitive actions (like processing payments or deleting data), you can require explicit user confirmation before executing a tool. When you configure user confirmation, the agent:- Explains what action it’s going to perform
- Asks for user confirmation (“Do you confirm you want to process the $50 refund?”)
- Waits for an affirmative response
- Only then executes the tool
Next Steps
Create HTTP Integration
Step-by-step guide to connect any REST API to your agents.
Create MCP Integration
Learn how to automatically sync tools from MCP servers.
Assign Integrations to Agents
Configure which agents can use which tools.
Use Tools in Prompts
Learn how to instruct your agents on when to use each tool.