Setting up workflows
Learn how to set up workflows in Revo. Create triggers, add steps, test runs, and automate tasks across Jira, Slack, meetings, and feedback to save time.
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.
Important: Make sure to toggle the workflow as active, otherwise, it won’t run even if it’s scheduled.
⚡ Event Trigger
Starts the workflow when something happens inside Revo. This could include actions such as:
A new document is created
A document is updated
A new task being created
A meeting is created
A memo is created
A photo document is created
A video document is created
🌐 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, you can either:
• Give Revo an instruction
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 mode (Default, Auto, Data Retrieval)
• Create a Jira ticket
The Jira node lets you create issues in Jira directly from a workflow. This makes it easy to turn meeting outcomes, feedback, or automated analysis into structured Jira tickets without manual copy-pasting.
How it works:
Project: Choose a Jira project yourself, or let Revo select based on context.
Issue Type: Define the type (Story, Task, Bug, Epic) or let Revo generate one automatically.
Assignee: Assign to a specific teammate, or allow Revo to recommend the right person.
Labels: Add labels for tracking, or let Revo generate them dynamically.
Custom Fields: Once you pick a project and issue type, you’ll see any available custom fields.
Additional Instructions: Provide extra guidance, e.g. “Add acceptance criteria” or “Include reproduction steps.”
You can either fill these fields manually or rely on “Generated by Revo” to have them auto-populated from the workflow context
• Send a message to Slack
Send results from your workflows directly into Slack channels. This can be a simple message, or the output of a previous workflow step (like a report, summary, or alert). It’s ideal for keeping teams updated in real time, for example:
Post a weekly progress summary in your #product channel.
Share a customer feedback report with #support.
Alert #engineering when new issues or risks are detected.
• Add a condition
Define a condition and, choose different next steps depending on whether the condition is true or false.
• Transform data
Tell Revo how to reshape or process data.
• Create an insight
Generate an Insight that appears in your Revo feed. The Create Insight step should just tell Revo how to present that transformed output in the feed.
• Update an Item
The Update Item step lets you modify an existing object in Revo (e.g. a Meeting, Insight, User Feedback, Issue, or Agent Context). Instead of creating a new item, you enrich or update fields on one that already exists.
• Analyze a video
Use this node to automatically analyze meeting recordings with both audio and visual AI. It goes beyond transcripts by capturing non-verbal signals, such as emotions, engagement, or hesitation.
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.
Private Workflows
Only the workflows you build can be made private. Team workflows created by others will always remain visible to the team.
How to make a workflow private:
Go to your Workflows list.
Right-click on the workflow you want to make private.
Select Make Private from the menu.
Once marked as private, the workflow will only be visible and accessible to you. No one else on your team will be able to view or run it.
Controlling Where Reports Go
Making a workflow private means only you can see or edit the workflow itself. But the results of that workflow are not automatically private — they depend entirely on where you choose to send them.
Keep results private → Send outputs to yourself only (e.g. a private Slack channel).
Make results public → Even if the workflow is private, you can configure the last step to post results into shared spaces (e.g. a team Slack channel, Confluence page, or Jira project).
When to use Private Workflows:
Drafting experimental or test workflows before rolling them out to the team.
Running workflows tied to personal tasks or sensitive data.
Keeping exploratory automations separate from official team workflows.
This gives you flexibility and control, you decide when (and if) a workflow should become visible to others.
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.
Last updated