Seventy plus actions
across every WorksBuddy agent

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.

The platform handles security internally between Revo and the WorksBuddy agents, with no configuration required on your side. No credentials, no addresses, no permission scopes to negotiate. Every action runs with the workspace's existing identity and respects every permission rule already set in the target agent so an action a user could not perform manually inside Lio is one their workflow cannot perform automatically either.

Yes, that is the entire point. A single workflow can trigger on a Lio lead, create a task in Taro, generate an estimate in Inzo, and trigger a Sigi document send all in one canvas, all chained, with data flowing cleanly between agents at every step. The result of one action becomes the input to the next.

Every action returns the complete record. A created task arrives with its ID, assignee, due date, priority, linked records, and any other field the task type carries. A new lead returns with ID, contact details, source, score, tags, and every custom field. A sent invoice returns with invoice number, client, line items, total, due date, and send status. Every field is a variable for downstream nodes.

Action errors are caught and surfaced with full context. A failed action returns a clear message invalid input, permission denied, target record not found and the workflow can retry on transient errors, branch on permanent ones, or stop with a notification to the owner. The execution log captures input, output, error message, and resulting path, so debugging is a search across one place.

The new action appears in the Revo library automatically, ready to use the moment the agent ships it. No provider package to update, no integration quietly breaking, no manual update step. The library always reflects what the agents offer right now, so the team gets new operations the same day they become available.