Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Vimeo

Vimeo integration for Flows360 workflows.

CategoryContent And Files
AuthenticationOAuth 2.0
Version0.2.0
Published scopes6 published scopes
Last updatedSeptember 24, 2026

Overview

Connect Vimeo with Flows360

Vimeo integration for Flows360 workflows.

Use the Vimeo 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 5 actions and 4 triggers.

Available actions

  • Upload Video
  • Delete Video
  • Add Video to Showcase
  • Add Video to Folder
  • Custom API Call

Available triggers

  • New Video I've Liked
  • New Video by Search
  • New Video of Mine
  • New Video by User

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: Vimeo
  • Package: @activepieces/piece-vimeo@0.2.0
  • Exact artifact digest: sha256:0de803fbdd9cb56cf13ef8ddae8a9f63b960eb8dd182441d5a39ec7c667436af
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

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

Action contracts

  • Upload Video (upload_video), Upload a video to your Vimeo account Classification: read.
  • Delete Video (delete_video), Delete a video from Vimeo Classification: read.
  • Add Video to Showcase (add_video_to_showcase), Adds an existing video to a user's showcase Classification: read.
  • Add Video to Folder (add_video_to_folder), Adds an existing video to a user's folder Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Video I've Liked, polling.
  • New Video by Search, polling.
  • New Video of Mine, polling.
  • New Video by User, polling.

Verification

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

Capability summary

AuthenticationOAuth 2.0
Supported objects9
Supported actions5
Triggers4

Authentication

Authentication method: OAuth 2.0

Required scopes

publicprivateedituploaddeleteinteract

Authentication profiles

connection · oauth2

OAuth scopes: public, private, edit, upload, delete, interact

Supported objects

ObjectReadWriteNotes
Upload Video Yes No Upload a video to your Vimeo account
Delete Video Yes No Delete a video from Vimeo
Add Video to Showcase Yes No Adds an existing video to a user's showcase
Add Video to Folder Yes No Adds an existing video to a user's folder
Custom API Call Yes No Make a custom API call to a specific endpoint
New Video I've Liked Yes No polling trigger declared by the pinned package.
New Video by Search Yes No polling trigger declared by the pinned package.
New Video of Mine Yes No polling trigger declared by the pinned package.
New Video by User Yes No polling trigger declared by the pinned package.

Supported actions

Upload Video · Read

Upload a video to your Vimeo account

upload_video · Risk: low · Retry: safe

Inputs

  • videoUrl · string · Required, URL of the video file to upload
  • name · string · Required, Name for the video
  • description · string · Optional, Description for the video
  • privacy · string · Optional, Privacy setting for the video
  • password · object · Optional
  • allowEmbed · boolean · Optional, Allow others to embed this video
  • allowDownload · boolean · Optional, Allow others to download this video (not available for free Vimeo users)
  • contentRating · string · Optional, Content rating for the video
  • folderId · string · Optional, ID of the folder to add the video to
  • language · string · Optional, Language code for the video
  • license · string · Optional, License for the video
Delete Video · Read

Delete a video from Vimeo

delete_video · Risk: low · Retry: safe

Inputs

  • videoId · string · Required
Add Video to Showcase · Read

Adds an existing video to a user's showcase

add_video_to_showcase · Risk: low · Retry: safe

Inputs

  • videoId · string · Required
  • showcaseId · string · Required, ID of the showcase to add the video to
Add Video to Folder · Read

Adds an existing video to a user's folder

add_video_to_folder · Risk: low · Retry: safe

Inputs

  • videoId · string · Required
  • folderId · string · Optional, ID of the folder to add the video to
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.

Triggers

New Video I've Liked · Poll

Triggers when you like a new video on Vimeo

New Video by Search · Poll

Triggers when a new video is added that matches a search query

Inputs

  • query · string
New Video of Mine · Poll

Triggers when you add/upload a new video

New Video by User · Poll

Triggers when another specified user adds a video

Inputs

  • userId · string

Setup

Setup

  1. Add the Vimeo 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.

OAuth scopes

  • public
  • private
  • edit
  • upload
  • delete
  • interact
  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-vimeo@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 5 actions and 4 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 Vimeo 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-vimeo@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