> For the complete documentation index, see [llms.txt](https://docs.helmut.de/helmut4-releases/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.helmut.de/helmut4-releases/v4.13.0/helmut4-components/streamdesigner/nodes/actions/third-party/vidispine/vidiflow/vidiflow-trigger-workflow.md).

# VidiFlow Trigger Workflow

The **VidiFlow Trigger Workflow** node starts a workflow in a VidiFlow system directly from a Helmut stream.

The node authenticates against the configured VidiFlow instance, triggers the specified workflow, and optionally monitors its execution until completion. Data can be passed to the workflow using a JSON payload, enabling seamless integration between Helmut and VidiFlow.

Typical use cases include triggering media processing workflows, quality control, transcoding, delivery, archive operations, or any other automation implemented in VidiFlow.

***

### Input Parameters

#### URL

The base URL of the VidiFlow system.

Example:

```
https://vidiflow.example.com/
```

***

#### Workflow Name

The name of the VidiFlow workflow that should be executed.

The workflow must already exist on the configured VidiFlow instance.

***

#### Workflow Version

Specifies the version of the workflow to execute.

This allows multiple versions of the same workflow to coexist while ensuring the correct version is triggered.

***

#### Run as User

(Optional)

Executes the workflow using the specified VidiFlow user account.

The user must exist in the VidiFlow system and have sufficient permissions to execute the selected workflow.

***

#### Scope

The OAuth scope requested when obtaining an access token.

The configured scope must match the permissions granted to the registered client application.

Example:

```
vidi api
```

***

#### Token Endpoint

The OAuth token endpoint used to request an access token.

Example:

```
authservice/connect/token
```

***

#### Client ID

The client identifier issued during application registration.

***

#### Client Secret

The client secret issued during application registration.

***

#### Payload

The JSON payload that will be passed to the VidiFlow workflow.

Wildcards may be used to dynamically construct the payload.

Example:

```
{
  "assetId": "{job.assetId}",
  "projectName": "{project.name}"
}
```

***

#### Progress Message

(Optional)

Dashboard message displayed while the VidiFlow workflow is running.

Example:

```
Workflow in progress
```

***

#### Done Message

(Optional)

Dashboard message displayed after the workflow has completed successfully.

Example:

```
Workflow successful
```

***

#### Timeout

Maximum time, in seconds, that the node waits for the workflow to complete.

If the timeout is exceeded while monitoring is enabled, the node fails.

***

#### Skip Monitoring

When enabled, the workflow is triggered and the node immediately continues without waiting for the VidiFlow workflow to finish.

When disabled, the node monitors the workflow execution and only continues after the workflow has completed successfully or failed.

This option is useful for long-running workflows that should execute independently of the Helmut stream.

***

### Typical Use Cases

* Triggering automated transcoding workflows.
* Starting quality control or compliance checks.
* Initiating archive or restore workflows.
* Launching delivery or distribution processes.
* Passing Helmut project, job, or asset information to VidiFlow for further processing.
* Orchestrating media workflows across Helmut and VidiFlow.

***

### Practical Tip

Use **Skip Monitoring** for workflows that may run for an extended period or continue independently of the Helmut workflow. This allows the Helmut stream to proceed immediately without waiting for the external workflow to complete.

When subsequent Helmut nodes depend on the successful completion of the VidiFlow workflow, leave **Skip Monitoring** disabled so that the stream waits for the final workflow result before continuing.