Seventy plus actions
across every WorksBuddy agent
70+ pre built actions across every WorksBuddy agent: tasks in Taro, leads in Lio, invoices in Inzo, documents in Sigi. No code.
From picking an action to a running step in 4 steps
Pick the agent, choose the action, map fields, run, use the result downstream. No credentials needed.
Pick the Action
Pick the agent and action
70+ pre built actions sit across the four WorksBuddy agents. Pick the agent, browse the categorised list, select the action. Each is named in business language, so finding the right one is reading a menu, not docs.
- Taro · Tasks
- Lio · Leads & Contacts
- Inzo · Billing
- Sigi · Documents
Map the Fields
Map fields from earlier steps
Every action opens a panel with the fields it needs. Drop variables from earlier steps into the inputs: the trigger lead name becomes the task assignee, the deal value flows into the estimate. Same visual mapping as everywhere.
- Variables Panel
- Visual Mapping
- Live Preview
- Validation as You Type
Run the Action
Run the action, no credentials needed
When the workflow reaches the action node, the platform handles the call to the target agent automatically. No credentials on your side, no addresses, no permissions in a separate dashboard. Revo and the WorksBuddy agents trust each other internally.
- No Credentials
- Platform Secured
- Instant Execution
- No Setup Step
Use the Result
Use the result downstream
The action returns the full record: the created task with ID and assignee, the new lead with score and tags, the sent invoice with number and due date. Every field becomes a variable, so the next step chains with no lookup.
- Full Response Available
- Variables Downstream
- Chain to Next Steps
- No Extra Lookups
Six reasons teams never go back
Once a team runs every WorksBuddy agent from one editor with no credentials or glue code, opening four apps makes no sense.
Every action your team needs
70+ pre built actions cover what every team runs: task creation and assignment, lead and contact management, billing, documents. The action you need is ready to enable.
No credentials to configure
The classic integration friction (credentials, permissions, testing connections) is gone. Revo and the agents trust each other, so actions work.
Cross agent workflows fully composable
A workflow can create a Taro task from a Lio lead, then an Inzo estimate on the same contact, then a Sigi document send. Four tools, one automation.
Map fields the same way every time
Every internal action uses the same mapping as every other step: same panel, same drag and drop, same validation. Learn one and you have learned them all.
Results flow straight downstream
Every action returns the full record as variables for every later node. The created task and sent invoice surface their IDs, so chains skip lookups.
Maintained by the platform itself
When a WorksBuddy agent ships a new action, it appears in Revo automatically. No provider package to update, no integration quietly breaking, no time spent on the seams.
15400+
Teams running cross agent actions
inside Revo
Built for teams running the full WorksBuddy stack together
Ops, sales, customer success, finance, and founders use Revo to let every WorksBuddy agent work together in one editor: Taro for tasks, Lio for leads, Inzo for billing, Sigi for documents. One toolkit, visual mapping.
Pre Built Actions
WorksBuddy Agents
Configuration
Execution
Every operation, every agent
70+ pre built actions span the four WorksBuddy agents: tasks in Taro, leads in Lio, billing in Inzo, documents in Sigi. Each is named in business language, configured the same way, and drops in without setup.
Every action, every agent
An internal action library in the platform. 70+ actions across four agents, zero config, visual mapping.
Taro Actions Task Management
Create a task, assign it, mark complete, add a comment, change priority, set due date, link to a deal. The full task toolkit as actions.
Lio Actions Lead & Contact Operations
Create a lead, update one, change stage, assign owner, create a contact, tag, add a note. The full lead and contact lifecycle as steps.
Inzo Actions Billing Operations
Create an estimate, send it, convert to an invoice, send, record a payment, mark paid, refund. Billing operations become a workflow step.
Sigi Actions Document Operations
Trigger a document send, request a signature, send a reminder, void, fetch status or the signed copy. Document workflows compose with the rest.
Pre Built, Zero Configuration
Every internal action is pre built. No credentials, addresses, permissions, or docs. Drop the action, map the fields, secured automatically.
Field Mapping Between Steps
Every action uses the same mapping as every other step. Drag variables into inputs, pick from autocomplete, confirm in the live preview.
Everything you need to know
Common questions on each agent's actions, security, cross agent chaining, and return values.
Which actions does each WorksBuddy agent expose?
Each agent ships a full set of operations. Taro covers tasks: create, assign, complete, comment, set priority and due date, link to a deal. Lio covers leads and contacts: create, update, change stage, assign owner, tag, note. Inzo covers billing: create and send estimates, convert to invoice, record payment, mark paid, refund. Sigi covers documents: send, request signature, remind, void, fetch status. The list crosses seventy and grows every release.
How is security handled for internal actions?
Can actions be chained across multiple agents in one workflow?
What does an action return when it runs?
What happens when an action runs into an error?
What happens when a new action ships in a WorksBuddy agent?