Setting up workflows

With Revo, you can automate repetitive tasks and save time by building intelligent workflows powered by a single AI agent - Revo itself. This guide walks you through the full process of creating, configuring, testing, and monitoring a workflow.

1. Open the Workflow Builder

• Navigate to Workflows from the left-hand panel.

• Click the ‘New Workflow’ button located at the top right of your screen.

2. Choose a Trigger Type

Your workflow begins with a trigger, which tells Revo when to start the workflow. You can choose from four types:

✅ Manual Trigger

• The workflow will only run when you manually click the ‘Run this workflow’ button.

• If you don’t trigger it manually, nothing happens—no result or report is generated.

🕐 Scheduled Trigger

• Choose the timezone, time of day, and days of the week when the workflow should run.

• Once configured, Revo will automatically execute the workflow at the set intervals.

• The results or reports will be sent or displayed according to the schedule.

⚡ Event Trigger

Starts the workflow when something happens inside Revo. This could include actions such as:

• A new task being created

• A user submitting feedback

• A document being uploaded

• Someone interacting with the app or browser extension

These are just a few examples. Revo continuously listens for a wide range of events across your workspace. When any of those events occur, it can automatically trigger your workflow—no manual action needed.

🌐 Webhook Trigger

Use this when you want the workflow to respond to an event happening outside of Revo (e.g. in another app or platform).

• An external service sends a real-time HTTP request to your workflow’s webhook URL.

• As soon as that happens—like a form submission, support ticket update, or code push—Revo receives the data and launches the workflow automatically.

3. Add Workflow Steps (Nodes)

After setting up your trigger, click the small circle at the bottom of the trigger card to start adding the next node (step).

For each step:

• Write your instruction in clear, plain English (or any language you prefer).

• You can configure:

  • The context Revo should refer to (e.g. User Stories, PRD, feedback..)

  • The LLM model to use (e.g. GPT-4, Claude..)

  • The mode (Default, Auto, Data Retrieval)

  • Whether you want to show Revo’s reasoning

To add the next step, just click the small circle at the bottom of the current node card. Keep doing this for each new instruction or action you want to include. Each click adds a new node where you can continue building your workflow step-by-step.

4. Test and Monitor Your Workflow

Test the Workflow

• For manual and scheduled workflows: click ‘Run this workflow’.

• For webhook and event triggers: simulate or perform the real action to test.

  • Example (webhook): Send a test payload from an external app to the webhook URL.

  • Example (event): Submit feedback or create a task in Revo to trigger the event.

Testing ensures your workflow behaves exactly as expected and is correctly triggered.

5. View Workflow Runs

Once a workflow has run, you can monitor and inspect its execution:

• Go to the Runs tab to see a full list of past executions.

• Click on any run to explore each node inside:

  • See the input Revo received at that step

  • The settings used (e.g. model, context)

  • The output Revo generated

This gives you full visibility into how Revo executed each instruction, making it easy to debug and improve your workflow over time.

Start Automating

You can now create as many workflows as you need to:

• Automate repetitive tasks

• Connect product signals across tools and teams

• Free yourself up for strategic and creative work

Revo workflows let you scale your thinking, your actions, and your time—automatically.

Want to experiment with a workflow?

If you have a workflow idea you'd like to prototype or test, you can use our dedicated Workflow Toolbox:

👉 Try it here → revo-toolbox.vercel.app/workflow

This sandbox allows you to simulate a Revo workflow in a test environment, helping you refine your use case before full implementation.