Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

VLM Run

VLM Run is a visual AI platform that extracts data from images, videos, audio, and documents. It helps automate analysis workflows, such as object detection, transcription, image/audio analysis, and document parsing.

CategoryBusiness Intelligence
Authenticationcustom
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 24, 2026

Overview

Connect VLM Run with Flows360

VLM Run is a visual AI platform that extracts data from images, videos, audio, and documents. It helps automate analysis workflows, such as object detection, transcription, image/audio analysis, and document parsing.

Use the VLM Run connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 6 actions and no declared triggers.

Available actions

  • Analyze Audio
  • Analyze Image
  • Analyze Document
  • Analyze Video
  • Get File
  • Custom API Call

Available triggers

  • No triggers are declared in this pinned package.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: VLM Run
  • Package: @activepieces/piece-vlm-run@0.2.0
  • Exact artifact digest: sha256:0c63355f18f7532a99dc80054c60024c5c4e37d2267d352c1fc92c5762098850
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Analyze Audio (analyzeAudio), Process an audio file, extracting features or transcription Classification: read.
  • Analyze Image (analyzeImage), Process an image (file or URL), extracting descriptions, detecting objects, etc. Classification: read.
  • Analyze Document (analyzeDocument), Process a document (PDF, DOCX, etc.), extracting structured data or text. Classification: read.
  • Analyze Video (analyzeVideo), Analyze a video file or URL, e.g. extract frames, detect content, etc. Classification: read.
  • Get File (getFile), Gets file's metadata by ID. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • No trigger delivery contracts are declared.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects6
Supported actions6
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Analyze Audio Yes No Process an audio file, extracting features or transcription
Analyze Image Yes No Process an image (file or URL), extracting descriptions, detecting objects, etc.
Analyze Document Yes No Process a document (PDF, DOCX, etc.), extracting structured data or text.
Analyze Video Yes No Analyze a video file or URL, e.g. extract frames, detect content, etc.
Get File Yes No Gets file's metadata by ID.
Custom API Call Yes No Make a custom API call to a specific endpoint

Supported actions

Analyze Audio · Read

Process an audio file, extracting features or transcription

analyze_audio · Risk: low · Retry: safe

Inputs

  • audio · object · Required, The audio file to get the transcription from. Only MP3 supported.
Analyze Image · Read

Process an image (file or URL), extracting descriptions, detecting objects, etc.

analyze_image · Risk: low · Retry: safe

Inputs

  • image · string · Required, The image file to be analyzed.
  • domain · string · Required, The specific analysis domain for the image.
Analyze Document · Read

Process a document (PDF, DOCX, etc.), extracting structured data or text.

analyze_document · Risk: low · Retry: safe

Inputs

  • document · object · Required, The document file to be analyzed.
  • domain · string · Required, The specific analysis domain for the document.
Analyze Video · Read

Analyze a video file or URL, e.g. extract frames, detect content, etc.

analyze_video · Risk: low · Retry: safe

Inputs

  • video · object · Required, The video file to be analyzed.
  • domain · string · Required, The specific analysis domain for the video.
Get File · Read

Gets file's metadata by ID.

get_file · Risk: low · Retry: safe

Inputs

  • fileId · string · Required, Select a file to retrieve its details.
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Setup

Setup

  1. Add the VLM Run connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-vlm-run@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 6 actions and 0 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required VLM Run connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-vlm-run@0.2.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com