> ## Documentation Index
> Fetch the complete documentation index at: https://docs.visotrust.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How VISO TRUST integrations work

> How VISO TRUST connects to your existing tools through event-driven native integrations, webhooks, and the REST API for automated TPRM workflows.

VISO TRUST integrations connect your third-party risk program to the tools your team already uses — so risk data flows into your workflows automatically, without manual export and import.

Integrations are managed in **Settings → Integrations**.

## How Integrations Work

VISO TRUST integrations are **event-driven**. When something happens in your program — an assessment completes, a risk advisory is surfaced, a vendor's status changes — VISO TRUST can automatically trigger an action in a connected system.

Examples:

* An assessment completes → a Slack message is sent to your security channel
* A new supplier is added in Coupa → the relationship is automatically created in VISO TRUST
* A risk-relevant event fires → a record is created or updated in a connected system

This event-to-action model is managed through **Automations** — configurable rules that define what triggers an action and what that action does.

## Connecting an Application

From **Settings → Integrations**:

1. Find the application you want to connect
2. Click **Connect** or **Manage Connection**
3. A secure authorization window opens — enter your credentials and complete the flow
4. Once connected, the integration status turns green

Depending on the integration, authentication is handled either through the provider's own authorization flow (for example, Slack) or with credentials you supply (for example, Coupa API keys), which are stored securely.

## Managing Automations

Each integration can have one or more **Automations** — rules that define how data flows between VISO TRUST and the connected application.

Each automation card shows:

* **Trigger** — the VISO TRUST event that starts the automation (e.g., "Assessment Completed")
* **Actions** — what happens when the trigger fires
* **Last Run** — when the automation last executed

<Note>
  Automations are powered by Workato and may need to be enabled for your organization. Contact your Customer Success Manager if you don't see them in Settings → Integrations.
</Note>

### Automation Actions

| Action        | Description                                                      |
| ------------- | ---------------------------------------------------------------- |
| **Launch**    | Starts the automation                                            |
| **Stop**      | Pauses the automation without deleting it                        |
| **View Runs** | Opens execution history — successes, failures, and error details |

Automations won't launch unless all required applications are connected. If an automation is failing, **View Runs** is the best place to start troubleshooting — it shows exactly what happened and any error details.

## Field Mappings

Some integrations support **field mappings** — configuration that controls how data from an external system maps into VISO TRUST (and vice versa). For example, you might map an external system's priority field to a VISO TRUST risk level.

Field mappings let you align integration behavior with your existing data model without custom development. They're configured per-integration in the connection settings.

## API and MCP

For custom integrations, VISO TRUST provides a public **REST API** under `/api/v1/*`. You can use it to:

* Programmatically create and update relationships
* Pull risk scores, assessment data, and advisory feeds into other systems
* Manage webhooks and lifecycle events from external tools

VISO TRUST also supports **Model Context Protocol (MCP)** for AI integration — allowing AI tools to query your VISO TRUST program data directly.

See [API Reference](/api-reference/authentication) for documentation on authenticating and using the APIs.

## Webhooks

Webhooks let you push VISO TRUST events to any external endpoint in real time — useful for building custom integrations with systems not covered by native connectors.

See [Webhooks](/integrations/webhooks) for setup and event schema documentation.