Native triggers from every Worksbuddy agent Lio, Taro, Sigi, and Inzo built directly into Revo. A new lead in Lio, a deal created in Taro, a document signed in Sigi, an invoice sent in Inzo: every event in every agent becomes a workflow trigger the moment you turn it on. Pre built, one click, no configuration required. A workflow automation platform that finally lets your own agents talk to each other without anyone wiring the plumbing first.
Pick the Worksbuddy agent the event will come from Lio, Taro, Sigi, or Inzo. Choose the trigger event from the pre built list for that agent. One click enables the trigger, with no addresses to copy, no secrets to share, no configuration to write. The next event of that type fires the workflow instantly, with the full record passed straight to every downstream node.
Pick the Agent
Four Worksbuddy agents sit natively inside Revo as first class trigger sources. Lio for lead and task events. Taro for deal and contact events. Sigi for document and risk events. Inzo for estimate and invoice events. Pick the agent that owns the event you want to react to, and Revo lists every pre built trigger that agent exposes, ready to enable.
Choose the Event
Each agent exposes a curated list of trigger events that match the actual moments your business cares about. New lead created, task completed, deal moved to next stage, contact updated, document signed, risk flagged on a contract, estimate created, invoice sent. The events are named the way your team already thinks about them, not the way an engineering schema document would phrase them.
One Click Enable
Click enable and the trigger is live. No webhook addresses to generate, no shared secrets to exchange, no permissions to grant in a separate dashboard, no documentation to read. Revo and the other Worksbuddy agents already trust each other, so the trigger goes from picked to active in the time it takes the click animation to finish.
Instant Reaction
The next event of that type in the source agent fires the workflow instantly, with the full record passed straight through to every downstream node. The new lead arrives with the contact details, the source, the score, the tags, and any custom fields the team added. The new invoice arrives with the client, the amount, the line items, and the due date. Every variable a downstream node could possibly want is already in scope.
Once a team has native triggers from every Worksbuddy agent pre built, one click, no plumbing the old pattern of wiring internal applications to an automation tool with addresses and secrets and configuration starts looking like work nobody should have to do. These are the changes that show up first.
Lio, Taro, Sigi, and Inzo are already inside Revo the moment you log in. There is no separate integration to install, no marketplace to visit, no provider to add. The cross agent workflow you wanted to build the day you signed up is buildable the day you sign up, instead of after a half day of getting the integration wired correctly.
One click enables a trigger. There is no webhook address to copy, no secret to paste, no permission scope to negotiate, no documentation to find buried inside another agent's admin panel. The fastest integration setup the team has ever experienced is the one for the agents the platform builds itself, which is exactly how it should be.
A new lead in Lio kicks off a deal in Taro. A signed document in Sigi fires the invoice in Inzo. A risk flagged in Sigi notifies the deal owner in Taro. The classic the data sits in one agent and the next step happens in another pattern that used to require a custom integration project becomes a five minute workflow build, in the natural language of the work itself.
Internal triggers do not poll. The moment the event happens in the source agent, it lands in Revo and the workflow starts running. The delay between a lead landing in Lio and the welcome email going out in your downstream workflow drops to the time it takes to render the email template not the next polling interval, not the next scheduled sync, just the time between the action and the reaction.
The trigger does not just say a new lead happened and leave the workflow to look it up. The full lead record the contact details, the source, the score, the tags, the custom fields arrives with the trigger, ready for every downstream node to use. The lookup step that other integrations always need at the start of every workflow simply disappears.
When an agent ships a new event type, the trigger for it appears in Revo automatically. When the event payload changes shape, the trigger updates in lockstep. There is no provider library that has fallen out of date, no integration that quietly breaks because somebody on the other side changed something, and no team time spent maintaining the seams between products that are all built in the same place.
Lio, Taro, Sigi, and Inzo are already inside Revo the moment you log in. There is no separate integration to install, no marketplace to visit, no provider to add. The cross agent workflow you wanted to build the day you signed up is buildable the day you sign up, instead of after a half day of getting the integration wired correctly.
One click enables a trigger. There is no webhook address to copy, no secret to paste, no permission scope to negotiate, no documentation to find buried inside another agent's admin panel. The fastest integration setup the team has ever experienced is the one for the agents the platform builds itself, which is exactly how it should be.
A new lead in Lio kicks off a deal in Taro. A signed document in Sigi fires the invoice in Inzo. A risk flagged in Sigi notifies the deal owner in Taro. The classic the data sits in one agent and the next step happens in another pattern that used to require a custom integration project becomes a five minute workflow build, in the natural language of the work itself.
Internal triggers do not poll. The moment the event happens in the source agent, it lands in Revo and the workflow starts running. The delay between a lead landing in Lio and the welcome email going out in your downstream workflow drops to the time it takes to render the email template not the next polling interval, not the next scheduled sync, just the time between the action and the reaction.
The trigger does not just say a new lead happened and leave the workflow to look it up. The full lead record the contact details, the source, the score, the tags, the custom fields arrives with the trigger, ready for every downstream node to use. The lookup step that other integrations always need at the start of every workflow simply disappears.
When an agent ships a new event type, the trigger for it appears in Revo automatically. When the event payload changes shape, the trigger updates in lockstep. There is no provider library that has fallen out of date, no integration that quietly breaks because somebody on the other side changed something, and no team time spent maintaining the seams between products that are all built in the same place.
Pre built triggers from Lio, Taro, Sigi, and Inzo. One click to enable. Full record passed to every downstream node. No setup, no secrets, no maintenance.
14600+
Teams composing across Worksbuddy agents
in Revo
Operations leaders, sales teams, customer success managers, finance specialists, and founders use Revo as the workflow automation platform that finally lets every Worksbuddy agent in their stack work together. Lio handles the leads. Taro handles the deals. Sigi handles the documents. Inzo handles the billing. Revo connects them with native triggers that need no setup, fire instantly, and pass the full record straight through to the downstream workflow. Every team a small business running two Worksbuddy agents or a larger organisation running all four across hundreds of business process automations gets the same one click connection between every agent and every workflow.
Native Agents
Events
Enable
Reaction
Lio for leads and tasks, Taro for deals and contacts, Sigi for documents and risk, Inzo for estimates and invoices. Every meaningful event in every agent appears in Revo as a pre built trigger, named in the business language your team already uses. Pick the agent, pick the event, enable in one click the cross agent workflow story finally feels native instead of glued together.
A complete internal trigger library built into the same workflow automation platform your team already uses. Four Worksbuddy agents, every meaningful event from each one, one click activation, instant firing, and the full record passed straight through to downstream workflow nodes.
Every meaningful event in Lio becomes a native trigger in Revo new lead created, lead updated, lead stage changed, lead assigned, task created, task completed, task overdue. Each trigger arrives with the full lead or task record so the downstream workflow has every contact detail, every tag, every custom field ready to use without an extra lookup step.
Sales motion events fire workflows the moment they happen deal created, deal moved to a new stage, deal closed won or lost, contact created, contact updated, pipeline value changed. The full deal record arrives with every fire, including the contact, the pipeline, the stage, the value, and the close probability, so cross agent revenue automations finally come together cleanly.
Document and contract lifecycle events surface as triggers in Revo document sent for signature, signed by a party, fully completed, declined, risk flagged on a clause, missing clause detected. The full document context comes through, including the parties, the document type, the risk findings, and the signature status, so contract workflows can branch on what actually matters.
Billing and accounting events trigger workflows in real time estimate created, estimate approved, invoice sent, invoice paid, payment received, payment overdue. The full billing record arrives with every fire, with the client, the line items, the total, the due date, and the payment status, so the finance side of every workflow stops needing a manual handoff in the middle.
Every internal trigger is pre built and ready to enable. No webhook addresses to generate, no secrets to share, no permissions to negotiate in another dashboard, no documentation to read. One click activates the trigger, and the next event of that type in the source agent fires the workflow immediately.
The trigger does not just say something happened and leave the workflow to look up the details. The complete record lead, deal, document, invoice arrives with the trigger and every field is available as a variable to every downstream node. The lookup step that other integrations always need at the start of every workflow disappears entirely.
Every meaningful event in Lio becomes a native trigger in Revo new lead created, lead updated, lead stage changed, lead assigned, task created, task completed, task overdue. Each trigger arrives with the full lead or task record so the downstream workflow has every contact detail, every tag, every custom field ready to use without an extra lookup step.
Sales motion events fire workflows the moment they happen deal created, deal moved to a new stage, deal closed won or lost, contact created, contact updated, pipeline value changed. The full deal record arrives with every fire, including the contact, the pipeline, the stage, the value, and the close probability, so cross agent revenue automations finally come together cleanly.
Document and contract lifecycle events surface as triggers in Revo document sent for signature, signed by a party, fully completed, declined, risk flagged on a clause, missing clause detected. The full document context comes through, including the parties, the document type, the risk findings, and the signature status, so contract workflows can branch on what actually matters.
Billing and accounting events trigger workflows in real time estimate created, estimate approved, invoice sent, invoice paid, payment received, payment overdue. The full billing record arrives with every fire, with the client, the line items, the total, the due date, and the payment status, so the finance side of every workflow stops needing a manual handoff in the middle.
Every internal trigger is pre built and ready to enable. No webhook addresses to generate, no secrets to share, no permissions to negotiate in another dashboard, no documentation to read. One click activates the trigger, and the next event of that type in the source agent fires the workflow immediately.
The trigger does not just say something happened and leave the workflow to look up the details. The complete record lead, deal, document, invoice arrives with the trigger and every field is available as a variable to every downstream node. The lookup step that other integrations always need at the start of every workflow disappears entirely.
Common questions about what events each agent exposes, what no configuration really means, how cross agent workflows work in practice, what data arrives with each trigger, whether you can filter at the trigger level, and what happens when an agent adds a new event type.
Each agent exposes a curated set of business level events that match the moments your team actually cares about. Lio covers lead and task events including new lead, lead updated, lead stage changed, task created, task completed, and task overdue. Taro covers sales events including deal created, deal stage changed, deal closed, contact created, and contact updated. Sigi covers document events including document sent, signed, completed, declined, risk flagged, and missing clause detected. Inzo covers billing events including estimate created, estimate approved, invoice sent, invoice paid, payment received, and payment overdue. New events are added regularly as the agents themselves grow.
Native triggers from Lio, Taro, Sigi, and Inzo. Pre built, one click, no configuration. Full record passed to every downstream node. The cross agent workflow story your team has been waiting for.