Internal App Triggers

Revo ships native triggers from every WorksBuddy agent: Lio, Taro, Sigi, and Inzo. The triggers are pre built and enable in one click with no configuration, and they fire workflows instantly with the full source record in scope.

How it works

Four WorksBuddy agents sit natively inside Revo. You pick an agent, choose a trigger event from a curated list named in business language, and click enable. There are no webhook addresses, shared secrets, separate permission dashboards, or documentation to find, because Revo and the other agents already trust each other.

Internal triggers do not poll. The moment an event happens in the source agent, it lands in Revo and the workflow runs with the complete record, so there is no lookup step at the start of the workflow. When an agent ships a new event type, the trigger appears in Revo automatically.

Key capabilities

• Lio triggers for lead and task events such as new lead, lead updated, stage changed, task created, completed, and overdue.
• Taro triggers for sales events such as deal created, moved, won or lost, and contact created or updated.
• Sigi triggers for document events such as sent, signed, completed, declined, risk flagged, and missing clause detected.
• Inzo triggers for billing events such as estimate created or approved, invoice sent or paid, and payment received or overdue.
• Pre built one click setup with no webhook addresses, secrets, or permissions.
• The full record passed to every downstream node with the trigger.
• Trigger level filter conditions that decide whether a workflow should fire.

Tips