Connectors
A connector gives an agent access to a business tool: read data, create a ticket or request an action. Available tools depend on the agent configuration and assigned permissions.
UserRequest to the agent
PlatformTool calls
AgentTools and call arguments
PermissionsAccount and agent access
Human approvalWhen required for the action
ConnectorAuthenticated service call
Business toolERP, CRM, DMS
API or MCP server
API or MCP server
Dedicated accessConnector identity and permissions
Activity recordsCalls and results
The connector calls the tool from the platform
The agent API works in the opposite direction: a third-party application calls SmartAGT. A connector lets SmartAGT call a third-party application.
What you prepare
| Item | Role |
|---|---|
| HTTPS endpoint | Address of the selected business API or MCP server |
| Connector identity | Account or access supplied by the business system |
| Permissions | Operations and data needed by the agent |
| Network and trust | Authorised destinations, optional proxy and service CA |
A connector can return data that becomes part of the model context. Selecting an external model must therefore account for the information accessible in connected tools.
Place in the PoC
The first PoC covers chat and a local document. Add connectors to demonstrate a specific business use. Their configuration and action approvals are described in the documentation inside the product.