AgentsTaro
How Taro connects
How Taro shares one data layer with other WorksBuddy agents and triggers work automatically.
Every WorksBuddy agent shares one data layer and can trigger the others automatically. Taro is wired into the suite so that delivery work flows in from sales and support, and project progress flows back out to forecasting, billing, and the CRM.
Automations Taro triggers
These are actions in Taro that automatically drive work in another agent.
| When this happens in Taro | Connected agent | What happens |
|---|---|---|
| A project milestone is hit | Inzo | An invoice is drafted with the milestone value, client details, and billing terms pre-populated. |
| Sprint velocity and task completion update | Moni | Revenue intelligence forecasts update in real time to reflect actual delivery pace. |
| A task is completed | Lio | The related deal stage updates so sales reps see live delivery progress in the CRM. |
Automations that trigger Taro
These are actions in other agents that automatically create or update work in Taro.
| When this happens | Source agent | What happens in Taro |
|---|---|---|
| A deal is won | Lio | A full onboarding project is created with tasks assigned to the CS team, plus due dates and priorities. |
| A support ticket is escalated | Zeni | A linked dev task is created with issue context, severity, and the original ticket attached. |
| A workflow trigger fires (for example a contract is signed) | Revo | A predefined batch of tasks is launched automatically. |
Build a custom automation
Custom cross-agent automations are built with Revo, the workflow automation agent. Revo fires task batches in Taro from a contract signature or any custom event, so you can connect Taro to the rest of the suite without manual handoffs.