Every WorksBuddy agent
connected from day one

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.

Exactly what it sounds like there is no setup work between picking the trigger and using it. No webhook address to generate, no shared secret to exchange, no permission scope to grant in another dashboard, no documentation to find, no test sequence to run. Revo and the WorksBuddy agents already trust each other, so the trigger goes from picked to active in the time it takes to click enable.

A workflow picks its trigger from one agent and its actions from any combination of the others. A new lead in Lio can create a deal in Taro, send a contract through Sigi, and schedule a follow up reminder all in one workflow, with the lead record flowing from Lio into each step. The workflow reads like the actual business process instead of a translation of it.

The full record arrives with the trigger, ready for every downstream node. A new lead trigger from Lio carries name, contact details, source, score, tags, and custom fields. A deal created trigger from Taro carries pipeline, stage, value, close probability, and contact. A document signed trigger from Sigi carries parties, document type, and signature timestamps. Nothing has to be looked up separately.

Yes. Every internal trigger supports filter conditions that decide whether the workflow should fire. Only fire when the lead source is Trade Show, when the deal value is above ten thousand dollars, when the document type is Master Services Agreement, when the invoice is overdue by more than seven days. The filter conditions appear in the trigger panel with the same field picker used everywhere else.

The new event appears in the Revo trigger list automatically, ready to use the moment the agent ships it. No stale provider library, no integration quietly breaking, no manual update step. The platform maintains the seams between its own agents so the trigger library always reflects what the agents offer.