Overview
This article walks you through the essential terms and capabilities of Hyver’s workflow automation features powered by Workato, a no-code automation platform. Whether you're setting up your first recipe or just curious how tasks are counted, this guide helps you speak the language of automation.
You’ll also find helpful links to Workato’s official documentation, so you can go deeper when needed.
Note: Workflow automation in Hyver is available to Premium customers. Only Hyver admins can create or manage workflows.
Key Terminology
Understanding how Workato operates will help you create smarter, more efficient automations. Here are the core terms you’ll see throughout Hyver's workflow engine:
Recipe
A recipe is an automated workflow built in Workato. It starts with a trigger and includes one or more actions that run in response. Recipes can integrate multiple applications and use logic such as conditions or loops.
Trigger
A trigger is the event that starts a recipe. It could be something in Hyver (e.g., a new high-risk finding) or an event in another tool (like a Jira ticket being closed).
Action / Step
An action is a task performed when a recipe is triggered. Actions include things like creating a Jira issue, sending a Slack message, or updating a finding in Hyver. Recipes can contain multiple steps and even call other recipes.
Connection
A connection enables a recipe to interact with external tools (like Salesforce or Teams). Once set up, connections remain available for use across multiple recipes.
Job
Each time a recipe is triggered, it runs as a job. A job holds the trigger data and runs the steps defined in the recipe. Jobs are useful for tracking what happened and when.
Task
A task is the basic unit of usage in Workato. Every time a recipe performs an action (such as an API call or file upload), that action counts as one task.
Note: not every step is a task—triggers and some internal operations don’t count.
What You Can Automate with Hyver
Hyver’s workflow automation supports outbound workflows — meaning Hyver sends information to other tools. However, some specific updates back to Hyver, like updating a finding’s status, are also supported through predefined actions. This includes:
Auto-Ticketing from Findings
Trigger: Hyver detects a critical security finding
Action: Create a Jira or ServiceNow ticket with full context
Result: No findings fall through the cracks.
Closed-Loop Remediation
Trigger: A Jira ticket is marked “Fixed”
Action: Update the linked finding in Hyver
Result: Dashboards and exposure metrics stay accurate automatically.
Alerts and Notifications
Trigger: A specific maturity gap is detected
Action: Send a message via Slack, Teams, or email
Result: The right people are notified instantly.
For more examples and integration ideas, explore Workato’s recipe library →
Important Notes
Admin-only access: Only Hyver admins can manage automation workflows.
Premium-only feature: Workflow automation is currently available to Premium customers.
Outbound only: Hyver sends data out. There’s no inbound data ingestion.
Task limits apply: Your company has a defined task allocation. Additional tasks may be purchased.
Wrap-up
Workflow automation is how Hyver helps you move from insight to action — without adding more to your plate.
If you're just getting started:
To explore the building blocks available in Hyver, check out these Workato references:
Think about where you lose time doing manual updates — that’s a great place to start automating
Explore what’s possible under Integrations → Workflow Automation in Hyver
Take your time or dive right in — either way, automation is here to make things easier.