Every WorksBuddy agent
connected from day one
Native triggers from every WorksBuddy agent Lio, Taro, Sigi, Inzo built into Revo. Pre built, one click, no configuration required.
From event in one WorksBuddy agent to a running workflow in 4 steps
Pick the agent, choose the event, one click enable. The next event fires the workflow instantly with the full record.
Pick the Agent
Pick the WorksBuddy agent
Four WorksBuddy agents sit natively inside Revo. Lio for leads and tasks, Taro for deals and contacts, Sigi for documents and risk, Inzo for estimates and invoices. Pick the agent and Revo lists every pre built trigger ready to enable.
- Lio · Leads
- Taro · Deals
- Sigi · Documents
- Inzo · Billing
Choose the Event
Choose the trigger event
Each agent exposes a curated list of events that match the moments your business cares about: new lead, task completed, deal moved, document signed, invoice sent. Events named the way your team already thinks.
- Curated Event List
- Business Language
- Real Moments
- No Schema Hunting
One Click Enable
One click, no configuration required
Click enable and the trigger is live. No webhook addresses, no shared secrets, no permissions in a separate dashboard, no documentation. Revo and the other WorksBuddy agents already trust each other.
- One Click Activation
- No Addresses
- No Secrets
- No Documentation
Instant Reaction
The workflow fires the moment it happens
The next event in the source agent fires the workflow instantly with the full record. A new lead arrives with contact, source, score, and tags. A new invoice arrives with client, amount, and due date. Every variable is in scope.
- Instant Trigger
- Full Record Passed
- All Fields in Scope
- No Lookup Steps Needed
Six reasons teams never go back
With native triggers from every WorksBuddy agent pre built, one click, no plumbing, the old way of wiring apps looks like needless work.
Every agent connected from day one
Lio, Taro, Sigi, and Inzo are inside Revo the moment you log in. No integration to install, no marketplace, no provider. Cross agent workflows are buildable day one.
No setup, no configuration
One click enables a trigger. No webhook address, no secret, no scope, no docs to find. The fastest setup is for the agents the platform builds itself.
Cross agent workflows finally make sense
A new lead in Lio kicks off a deal in Taro. A signed document in Sigi fires the invoice in Inzo. One agent triggering the next is a five minute build.
Events arrive instantly
Internal triggers do not poll. The moment the event happens in the source agent, it lands in Revo and the workflow runs. The delay drops to nothing.
The full record comes with the trigger
The trigger does not just say "new lead" and leave you to look it up. The full record (contact, source, score, tags) arrives with it. The lookup step disappears.
Built and maintained by the platform
When an agent ships a new event type, the trigger appears in Revo automatically. When the payload changes, the trigger updates in lockstep. No broken seams.
14600+
Teams composing across WorksBuddy agents
in Revo
Built for teams running the whole WorksBuddy stack together
Ops, sales, customer success, finance, and founders use Revo to let every WorksBuddy agent work together. Lio handles leads, Taro deals, Sigi documents, Inzo billing. Revo connects them with native triggers.
Native Agents
Events
Enable
Reaction
Four agents, every event covered
Lio for leads and tasks, Taro for deals and contacts, Sigi for documents and risk, Inzo for estimates and invoices. Every event is a pre built trigger named in business language.
Every agent, every event
An internal trigger library inside the platform. Four agents, every meaningful event, one click activation, instant firing.
Lio Triggers
Every meaningful event in Lio becomes a native trigger: new lead, lead updated, stage changed, task created, completed. Each arrives with the full record.
Taro Triggers
Sales events fire instantly: deal created, moved, won or lost, contact updated. The full deal arrives with contact, pipeline, stage, and value.
Sigi Triggers
Document lifecycle events as triggers: sent, signed, completed, declined, risk flagged. Full context (parties, type, status) comes with each.
Inzo Triggers
Billing events trigger in real time: estimate created, approved, invoice sent, paid, overdue. The full record arrives with client, total, and status.
Pre Built One Click Setup
Every internal trigger is pre built. No webhook addresses, no secrets, no permissions, no docs. One click activates and the next event fires it.
Full Record Passed to Downstream
The trigger does not just say "something happened" and leave you to look up details. The complete record arrives with it, every field a variable.
Everything you need to know
Questions about events per agent, zero config, cross agent workflows, and trigger data.
What events does each WorksBuddy agent expose?
Each agent exposes a curated set of business level events. Lio covers lead and task events: new lead, lead updated, stage changed, task created, completed, overdue. Taro covers sales events: deal created, stage changed, closed, contact updated. Sigi covers document events: sent, signed, completed, declined, risk flagged. Inzo covers billing events: estimate created, invoice sent, paid, overdue. More are added as the agents grow.
What does no configuration required really mean?
How do cross agent workflows work in practice?
What data arrives with each trigger?
Can I filter at the trigger level?
What happens when an agent adds a new event type?