Skip to main content

​
Overview

Connectors serve as organized libraries or “folders” that group agents by business function, software ecosystem, or specific use cases. Instead of managing hundreds of disconnected agents, Connectors allow you to package them into a ready-to-consume suite. For example, you could create a Zoho Books Connector containing over 100 specialized agents—each handling a different task like “Create Invoice,” “Fetch Customer,” or “Update Ledger”—providing a comprehensive toolkit for that specific platform.

​
Connector Composition

A Connector is not a new type of logic; rather, it is a container for the six standard agent types. A single Connector can house a mix of:
  • No-Code Agents for general Zoho queries.
  • External ERP Agents for direct API data sync.
  • Python Agents for custom data formatting.
  • File Search Agents for analyzing uploaded Zoho reports.

​
Configuring a Connector

When building a new Connector, you define the metadata that helps other users in your organization discover and use the library.

​
Linking Agents to Connectors

The relationship between an agent and a connector is defined at the moment of agent creation.

​
Steps

  1. Select Connector: When creating a new agent, you must select the parent Connector from a dropdown list.
  2. Inheritance: The agent inherits the context and categorization of the Connector.
  3. Availability: Once saved, the agent appears within the Connector’s library, ready to be dragged and dropped into any Workflow.

​
Benefits of Connectors

​
1. Modular Organization

Avoid “agent sprawl” by keeping your workspace clean. Agents are logically separated by the systems they interact with.

​
2. Rapid Workflow Building

When building a workflow, you can browse by Connector (e.g., “Open the Salesforce Connector”) to find exactly the agent you need, rather than searching through a global list of all agents.

​
3. Versioning & Logic Isolation

By grouping agents into a Connector, you can manage updates to a specific business process without impacting unrelated agents in the platform.
Pro-Tip: Use the “Documentation Links” field to link to the official API references of the external service. This helps workflow builders understand the data structures the agents are interacting with.