Project Structure for Enterprise AI Agent Development
A well-organized project structure is the prerequisite for collaborative agent development at scale.
The Standard Project Structure
Enterprise agent projects on Workato follow a consistent structure: one Project per agent or agent family, organized by business function and then by agent type. Within each Project: a Genie configuration, a Skills folder, a Knowledge Bases folder, and a Connections folder.
Project Boundaries
Each Project should contain one agent and its associated resources. Don't combine multiple unrelated agents in one Project — it makes access control, testing, and maintenance harder. The exception: closely related agents that share a Skill library and are governed together (e.g., all IT support agents) may share a Project.
Shared vs. Agent-Specific Resources
Some Skills and Knowledge Bases are used by multiple agents. Create a "Shared Resources" Project for these — Skills and Knowledge Bases that cross agent boundaries. Individual agent Projects reference the shared resources; they don't duplicate them. Duplication is how inconsistency enters the system.
Connection Management
All connections (Salesforce credentials, ServiceNow credentials, etc.) should be managed centrally by the platform team, not created by individual agent developers. Agent developers reference existing connections; they don't create new ones. This is the technical enforcement of the center-of-excellence governance model.
Environment Structure
Maintain at least two environments: Development and Production. Agent developers build and test in Development. Code reviews and approvals gate promotion to Production. Never build directly in the Production environment.