Introduction to Merge Agent Handler
Agent Handler includes:- Prebuilt connectors for common enterprise systems
- Built-in authentication and credential handling
- Observability and data-loss prevention controls
Key concepts
The high level flow of Merge Agent Handler is: you register a user so they can connect to third party data providers. That user then takes actions through your agents. As users take actions, Merge Agent Handler scans tool inputs and responses for sensitive data, and prevents data misuse based on configurations you set in the platform. Below are the key concepts of Merge Agent Handler:| Concept | Description |
|---|---|
| Registered User | The users who will be interacting with your agent. You can create these programmatically. |
| Connectors | The third-party systems that your customers will interact with. Examples: Jira, Linear, and Asana. |
| Tools | The specific actions within a connector that your customers can take. Examples: Create_Issue tool in Jira, a Get_Issue tool in Linear, or a Create_Task tool in Asana. |
| Tool Pack | The bundling of connectors and specific tools that your customers can use through your agent. |
| Link | UI component that guides your app’s user through authentication for a connector. |
| Connector Studio | The suite to add or customize connectors and tools for your different use cases. |
| Security Gateway | The security gateway scans tool inputs and responses for sensitive data, and takes action based on what’s configured within the platform. |