Maintain the Finding ID Across Tools
The Finding ID is the anchor that allows Hyver to map external actions back to the right asset.
When creating external tickets (e.g., Jira, ServiceNow), always:
Store the Finding ID in a custom field, or
Save it in the ticket description
Without this, Workato cannot reliably perform updates (such as changing the finding status).
Mapping Custom Fields (Jira Example)
Some workflows require mapping additional data between Hyver and Jira.
Steps:
In Jira, create a Custom Field (e.g., "Hyver Finding ID").
Add the field to the relevant Screens for the selected project.
In Workato, open the Create Jira Issue action.
Select your Project — Workato will sample the project to retrieve custom fields.
Once fields appear, map:
Hyver Finding ID→ Hyver Finding IDAny other fields you want to sync
If a field doesn’t appear, re-sample the project or refresh the connection.
Adding If-Conditions in Recipes
IF conditions allow you to build branching logic, such as syncing only when certain severities or statuses change.
Common use cases:
Only create Jira tickets for High or Critical findings.
Only update Hyver if status transitions to a specific state.
Map Jira statuses to Hyver statuses (e.g., Done → Fixed).
How to add IF conditions:
In your recipe, click + under any step.
Select If.
Define your condition, for example:
Finding severityequals “High”
Add the steps for the true branch.
(Optional) Add fallback steps for the false branch.
This ensures your workflows are precise and reduce unnecessary updates.
Adding Lookup Tables in Recipes to Map
Why you need a Lookup Table
When integrating Hyver with Jira using Workato, you often need to translate values between the two systems because they do not always use the same “language” for statuses.
In short: IF conditions decide when something should happen; Lookup Tables decide how to translate values when it happens.
Step-by-step: Configure a Lookup Table in Workato
Step 1: Open Lookup Tables
In Workato, go to Tools.
Select Lookup tables.
Step 2: Create a new Lookup Table
Click Create lookup table.
Name the table clearly, for example:
Hyver finding status → Jira issue status(Recommended) Add a description, such as:
“Maps Hyver finding statuses to Jira workflow statuses for Hyver-Jira sync recipes.”
Step 3: Define the columns
Create two columns:
Key column:
hyver_statusValue column:
jira_status
Step 4: Add mapping rows
Add one row per mapping. Example:
hyver_status | jira_status |
Open | To Do |
In Progress | In Progress |
Fixed | Done |
Ignored | Won’t Do |
Step 5: Save
Click Save (or Update) to publish the table.
Step-by-step: Use the Lookup Table in a Recipe
Below is a practical pattern for using the Lookup Table inside a Hyver → Jira sync recipe.
Note - A predefined template using Lookup table is available. Template name: “When a Jira issue status is updated, Update the related finding in Hyver” .
Step 1: Identify the Hyver status value in your recipe
Typically, your trigger or earlier step returns the Hyver finding status, for example:
Finding status=Open,Fixed, etc.
Step 2: Add a Lookup Table step
In your recipe, click + under the step where you need the Jira status.
Select ‘Action in app’
Search for Lookup tables by Workato
Select the action Lookup by key (naming can vary slightly by Workato UI).
Configure:
Lookup table:
Hyver finding status → Jira issue statusKey: map the Hyver field, e.g.
Finding status
This step returns the mapped Jira status (or transition ID), which you can use downstream.
Step 3: Apply the mapped value to Jira
Depending on your Jira configuration, you will do one of the following:
Option A: Set status during issue creation
In Create issue step, set the status field (if your Jira connector/workflow allows direct setting).
Option B: Transition the issue
Add a Jira: Transition issue step.
Use the lookup output (often best as a transition ID or transition name, depending on your Jira setup).
Step 4 (Recommended): Add a fallback for unmapped statuses
Lookup tables are only as complete as the mappings you define. To avoid silent failures:
Add an IF condition checking whether the lookup returned a value.
If empty, either:
set a default Jira status (e.g., “To Do”), or
log an error / notify a channel, or
stop the job with a clear message.
This prevents undefined Hyver statuses from breaking the sync.
Optimize Performance with Job Batching
When Hyver generates a large number of findings in a short period (for example, after a bulk import or automated scan), creating external tickets one-by-one can result in unnecessary load and slower processing times.
To handle high-volume workloads efficiently, we recommend using batch-oriented approaches in Workato, such as bulk actions when supported by the target system.