Workflows: Automating Tasks from Meetings, Email & Business Data

Workflows are custom automations that execute multi-step tasks without manual effort. Unlike basic scripts, Revo Workflows combine structured logic with AI intelligence to handle complex, context-aware automations.

Why this matters for email:

Workflows can analyze incoming customer feedback, create Jira tickets automatically, and trigger email responses or Slack updates. When a support email arrives, a workflow can route it, draft the reply using relevant product context, and log the issue, all before you even see it.

Structure: Trigger → Steps (Nodes) → Action
​
​Example: Meeting ends → Extract action items → Create Jira tickets → Post summary to Slack
​

Navigation:
Click Workflows in the left sidebar to see your automation library. From here you can:

Your workflow begins with a trigger that tells Revo when to run. You can choose from six trigger types:

Manual Trigger
Start the workflow only when you manually click "Run this workflow." Useful for on-demand reports or testing before scheduling.

Scheduled Trigger
Set timezone, time of day, and days of the week for automatic execution (e.g., Every Monday at 9 AM for weekly reports).

Important: Toggle the workflow to "Active" or it won't run even with a schedule set.

Event Trigger
Starts automatically when something happens inside Revo. Available event options:

Webhook Trigger
Respond to events from external apps. An outside service sends an HTTP request to your workflow's unique webhook URL, triggering the automation instantly (e.g., form submission, support ticket, code push).

Slack Trigger
Start the workflow based on Slack events like a message posted in a specific channel, a reaction added, or a command typed.

User Input
Allow users running the workflow to provide specific information before execution (e.g., date range for a report, customer name for analysis).

Click the small circle at the bottom of the trigger card to add nodes. Each node represents one step in your automation:

Revo Node
Give AI instructions in plain language (e.g., "Summarize the meeting and extract action items").

Jira Node
Create issues in Jira with auto-filled fields (project, issue type, assignee, labels, custom fields) based on workflow data or AI-generated content.

Confluence Node
Create pages in Confluence directly from workflow outputs. Useful for auto-generating documentation, meeting recaps, or knowledge base articles.

Send Email Node
Send automated emails to specific recipients with content generated from previous workflow steps (summaries, reports, alerts).

Slack Node
Post messages, summaries, or alerts to specific Slack channels based on workflow results.

Condition Node
Create branching logic with "if/then" statements (e.g., "If priority is High, notify the CTO in Slack. Otherwise, create a standard ticket").

Transform Node
Reshape, filter, or restructure data from previous steps before passing it to the next node. Useful for formatting outputs or extracting specific fields.

Create Insight Node
Generate a saved analysis or report in your Revo Insights feed. Perfect for weekly digests, competitive analysis, or strategic summaries.

Update Item Node
Modify existing Revo objects (meetings, issues, insights, user feedback, agent contexts) by updating specific fields with new values.

Analyze Video Node
Process meeting recordings using both visual and audio AI to detect emotions, engagement levels, hesitation, or non-verbal signals beyond the transcript.

Best practice: Use one clear instruction per node. Combining multiple tasks in a single node can produce inconsistent or unpredictable results.

For manual/scheduled workflows: Click Run this workflow to test execution
​For event/webhook triggers: Perform the real action (e.g., create a test meeting or send a webhook payload)

Review the output to ensure each step executed correctly.

Go to the Runs tab to see execution history. Click any run to inspect:

This visibility makes debugging and improving workflows straightforward.

Trigger: Meeting ends (event trigger)

Steps:

Email impact: When a customer emails asking "What are the next steps from our call?" Revo's draft references the auto-generated action items and ticket numbers from the workflow.

Trigger: Every Friday at 5 PM (scheduled)

Steps:

Email impact: When customers report issues, Revo's email drafts can reference "We've heard similar feedback from 12 customers this week and have prioritized a fix for next sprint."

Trigger: 5 days before scheduled release (scheduled based on cycle end date)

Steps:

Email impact: Stakeholder emails asking "Are we ready to ship?" get drafted responses citing actual blocker count, documentation status, and risk assessment.

Begin with a basic two-step workflow (e.g., Meeting ends → Send summary to Slack) before adding complex conditions and branches.

Each workflow should solve one clear problem. Instead of one massive "do everything" workflow, create specialized automations for specific needs.

Check the Runs tab weekly. If a step consistently fails or produces poor output, refine the instruction or add more context sources.

By default, workflows are visible to your entire team. You can make a workflow private if it's experimental or tied to personal tasks.

How to make private:

Important: Private workflows are only editable by you, but the results (where reports go) depend on your output settings. You control whether results go to private channels or shared team spaces.