Getting Started with Integrations in VISO TRUST

Overview

VISO TRUST integrations allow you to automatically connect your risk management workflows with the tools your teams already use - such as Jira and Slack - to reduce manual effort and keep stakeholders informed.

This article explains how to:

• Enable and manage integrations
• Connect your applications securely
• Understand and manage automations
• Troubleshoot common issues

Accessing Integrations

To access integrations, you must be an Org Admin in VISO TRUST.

Steps

1. Log in to the VISO TRUST platform
2. Navigate to:
   Settings → Integrations

From this page, you can view:

• Available integrations
• Connection status for each application
• Automations associated with your integrations

Connecting an Application

Supported Integrations

Common integrations include:

• Jira
• Slack
• VISO TRUST API (used internally to power automations)

Additional integrations may be available depending on your configuration.

How to Connect

1. From the Integrations page, locate the application you want to connect
2. Click Connect or Manage Connection
3. A secure connection window will open
4. Enter your application credentials
5. Complete the authorization flow

Once connected:

• The integration status will turn green
• The application will appear under Connected

Security note: VISO TRUST does not store or view your credentials. All authentication is handled securely.

Understanding Automations

Automations allow VISO TRUST to take action automatically when specific events occur, such as completing a risk assessment.

Automation Cards

Each automation card displays:

• Trigger – the event that starts the automation
• Actions – what happens when it runs
• Last Run – the most recent execution time
• Status – whether the automation is active or stopped

Managing Automations

Available Actions

Launch Starts the automation.

Stop Pauses the automation.

View Runs

• View execution history
• Review successes or errors

Automations cannot be launched unless all required applications are connected.

Viewing Automation History

Click View Runs on any automation to see:

• When the automation ran
• Whether it succeeded or failed
• Error details (if applicable)

This is the best place to start when troubleshooting unexpected behavior.

Event-Based Integrations (How Data Flows)

VISO TRUST integrations are event-driven.

Examples of events include:

• Risk assessments completed
• Vendor status changes
• Risk findings identified

When an event occurs:

1. VISO TRUST sends the event securely
2. The automation processes the event
3. Actions are taken (for example, creating a Jira ticket or sending a Slack message)

Field Mappings (Advanced Configuration)

Some integrations support dynamic field mappings, which allow you to control how data from an external system (such as Jira) is mapped into VISO TRUST.

Field mappings help align your existing workflows and data models without requiring custom development.

What Are Field Mappings?

Field mappings define how information from a source system (for example, a Jira issue) is mapped into specific fields within VISO TRUST when an automation runs.

Examples include:

• A Jira issue field populating a vendor name
• A Jira description mapping to a VISO TRUST description field
• A Jira key stored as an external reference ID

When available, field mappings can be accessed directly from the automation card.

How to Configure Field Mappings

1. Navigate to Integrations
2. Locate the automation you want to configure
3. Click Field Mappings
4. For each VISO TRUST field:
   • Select the source system (for example, Jira)
   • Choose the source field to map from
5. Click Save changes

Once saved, these mappings will be applied automatically each time the automation runs.

When to Use Field Mappings

Field mappings are useful when:

• Your Jira instance uses custom fields
• You want control over which Jira fields populate VISO TRUST records
• Different teams use different naming conventions
• You want to reuse the same automation across multiple projects

Current Limitations to Be Aware Of

Field mappings are intentionally designed to be simple, predictable, and safe. There are a few important limitations to understand.

No Field Transformations

The field mapping interface does not support data transformations.

Examples of unsupported transformations include:

• Splitting a single field into multiple fields
  (for example, extracting first and last names from an email address)
• Reformatting values
• Applying conditional logic

Example:

• Jira Submitter → returns an email address
• VISO TRUST requires:
  • First Name
  • Last Name
  • Email

This type of transformation cannot be performed in the field mapping interface.

No Merging Multiple Fields into One

You cannot combine multiple source fields into a single destination field.

Examples include:

• Combining multiple Jira fields into one Tags field
• Concatenating text from several fields into one description

Each destination field can only map from one source field.

Best Practices

• Map fields that are already aligned in structure and format
• Prefer single-purpose fields over overloaded fields
• Use consistent Jira field definitions across projects when possible
• Validate mappings after changes by reviewing automation runs

If your use case requires transformations or complex logic, contact VISO TRUST Support to discuss alternative approaches.

Troubleshooting Field Mappings

If an automation does not behave as expected after updating field mappings:

1. Confirm all required fields are mapped
2. Ensure source fields exist and contain data
3. Review recent runs using View Runs
4. Verify the automation is running

Common Troubleshooting Scenarios

An Automation Will Not Start

Check the following:

• All required integrations are Connected
• The automation is not already running
• Credentials have not expired or changed

An Automation Failed

1. Click View Runs
2. Review the error message
3. Confirm your integration credentials are still valid

If the issue persists, contact VISO TRUST Support.

Security & Permissions

• Credentials are entered and managed by you
• VISO TRUST does not have access to your passwords or tokens
• Each customer’s integrations operate in a secure, isolated environment

Getting Help

If you need assistance, contact VISO TRUST Support and provide:

• The integration name
• The automation name (if applicable)
• The time the issue occurred
• A screenshot or error message

Summary

With VISO TRUST integrations, you can:

• Connect your existing tools securely
• Automate risk workflows
• Reduce manual effort
• Gain better visibility across teams

Integrations are designed to be easy to manage, secure by default, and fully under your control.