Every lead, every channel, in the same flow.

Three things. First, Revo is the native automation engine inside the WorksBuddy suite — Lio, Taro, Sigi, Inzo, and Evox are first-class apps with full trigger and action surfaces, not third-party connectors. Second, every workflow runs on Temporal.io for durable execution, automatic retries, and full state recovery — Zapier silently fails, Revo doesn't. Third, you get 1000+ external apps via Pipedream Connect plus a Developer Console to register your own apps, so you're not stuck waiting for a connector to ship.

Not yet. The OpenAI SDK is wired into the codebase as a foundation, but AI features are not active in the platform at this time. On the roadmap: workflow generation from plain-English descriptions, AI-suggested next step nodes while building a workflow, and AI-powered error explanations on failed executions. We'll ship these when they're real, not before.

Four kinds. Webhook triggers from GitHub, Stripe, Slack, Shopify, GitLab, or any custom source — with HMAC signature verification on inbound payloads. Pipedream app triggers for 1000+ external apps (Gmail new email, GitHub new commit, Google Sheets new row, etc.). Internal app triggers fired directly from Lio, Taro, Sigi, Inzo, and Evox. And manual triggers for workflows run on demand by clicking a button. Each trigger comes with the full event payload available in variable interpolation downstream.

Every workflow runs on Temporal.io. Steps are distributed across workers. Failed steps retry automatically with exponential backoff. Workflows mid-run survive deploys because state is persisted at every checkpoint. If Temporal itself is unavailable, a local fallback engine takes over so nothing stops. Each step writes a row to the execution_logs table for full audit and replay. Workflow runs can be aborted, paused, or resumed mid-flight from the UI.

Yes. The Developer Console lets any third-party app self-register with Revo. Each registered app gets a client_id, client_secret, and jwt_secret to authenticate. Developers define their own triggers (events the app emits) and actions (operations Revo can invoke). Once registered, the app appears as a first-class building block in the visual workflow builder — anyone in your org can use it in workflows alongside Lio, Taro, and the 1000+ external apps.

Both. The primary surface is a drag-and-drop visual builder — pick a trigger, add action nodes, wire data between them with variable interpolation ({{trigger.data.field}}), add IF/ELSE conditions with 14 operators, test each step against real APIs before saving. For developers, every workflow can be exported as JSON, version-controlled in git, and re-imported in another environment. Long-lived API tokens let you trigger workflows programmatically. The visual builder and the JSON are equivalent — pick the right surface for the right job.

Three patterns. Internal WorksBuddy apps (Lio, Taro, Sigi, Inzo, Evox) authenticate via runtime JWT tokens minted per workflow step — every app has its own secret. External Pipedream apps authenticate via the user's connected OAuth account, brokered through Pipedream Connect. Custom apps registered through the Developer Console authenticate with their own client_id/client_secret/jwt_secret. Webhook payloads are HMAC-signature-verified at the edge before any step runs.