Hyver’s Workflow Automations allow you to integrate your security and compliance workflows with external systems such as Jira, ServiceNow, and collaboration tools. Workato serves as the underlying automation engine, enabling bi-directional synchronization.
This guide explains how to connect Hyver to Workato, build common recipes, and follow best practices to ensure maintainability and accuracy.
1. Connect Workato to the Hyver Connector
Before creating any automation, you must authenticate the Hyver connector in Workato.
Step 1: Retrieve your Hyver access token
In Hyver, go to Settings → Access token.
Generate a new Access Token or copy an existing one.
Store it somewhere secure - this token grants full API permissions.
Step 2: Connect the Hyver connector in Workato
In Workflow Automations, navigate to Create → Connection.
Search for the Hyver Connector.
Paste your Hyver Access Token into the required field.
Click Connect.
Once authenticated, your recipes can read triggers from Hyver and push actions back into your workspace.
2. Create a Recipe Triggered by a New Finding (Hyver → Jira → Hyver)
This example shows how to automatically create a Jira ticket when a new finding is discovered and then link the ticket URL back to Hyver.
Trigger:
New finding created (Hyver)
Action 1:
Create Jira issue
Choose the appropriate Jira connection.
Select the Project and Issue type (e.g., Bug, Task, Story).
Map fields:
Summary →
Finding titleDescription →
Finding descriptionPriority → map based on finding severity (optional)
Custom fields → map as needed (see section 4.2)
Action 2:
Send ticket URL/ID to Hyver
Use the action Send ticket URL/ID from the Hyver connector.
Map:
Finding ID →
Finding IDfrom the triggerTicket URL or Ticket ID → output from the Jira action
Source app - add the app name where the ticket ID derived from to ensure visibility in Hyver
This ensures the finding record in Hyver references the external ticket for full traceability.
3. Recipe: Update Hyver When an Issue Changes in Jira (Jira → Hyver)
This recipe listens for status updates in Jira and syncs them back to Hyver.
Trigger:
Issue updated (Jira)
Action:
Update Finding Status (Hyver)
Map the Finding ID — this must be maintained from the earlier recipe.
Map the New Status, ensuring it matches one of Hyver’s permitted statuses:
Open
To Do
In Progress
Reopen
On Hold
Fixed
Acceptable Risk
Not Relevant
Important:
Use a Workato lookup table or IF conditions (see Section 4.3) to translate Jira statuses (e.g., Done, Backlog, Blocked) into valid Hyver statuses.