Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Vidnoz

AI video generation platform

CategoryArtificial Intelligence
Authenticationcustom
Version0.0.8
Published scopes0 published scopes
Last updatedSeptember 30, 2026

Overview

Connect Vidnoz with Flows360

AI video generation platform

Use the Vidnoz 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 2 actions and 1 trigger.

Available actions

  • Generate Video with Avatar
  • Generate Video with Template

Available triggers

  • New Generated Video

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: Vidnoz
  • Package: @activepieces/piece-vidnoz@0.0.8
  • Exact artifact digest: sha256:e55d8b6afd3d70474773e179ccdb074d4435c312aef475ba0252061d8168b3a3
  • 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

  • Generate Video with Avatar (generate_video_with_avatar), Generate a video from an avatar. Classification: read.
  • Generate Video with Template (generate_video_with_template), Generate a video using a template. Classification: read.

Trigger contracts

  • New Generated Video, polling.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

Authenticationcustom
Supported objects3
Supported actions2
Triggers1

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Generate Video with Avatar Yes No Generate a video from an avatar.
Generate Video with Template Yes No Generate a video using a template.
New Generated Video Yes No polling trigger declared by the pinned package.

Supported actions

Generate Video with Avatar · Read

Generate a video from an avatar.

generate_video_with_avatar · Risk: low · Retry: safe

Inputs

  • name · string · Optional
  • aspect · string · Optional
  • avatarId · string · Required, Select the avatar to use.
  • avatarStyle · string · Optional
  • avatarCircleBgColor · string · Optional
  • avatarScale · number · Optional
  • avatarOffsetX · number · Optional
  • avatarOffsetY · number · Optional
  • voiceMode · string · Required
  • voice · object · Required
  • backgroundMode · string · Required
  • background · object · Required
Generate Video with Template · Read

Generate a video using a template.

generate_video_with_template · Risk: low · Retry: safe

Inputs

  • name · string · Optional
  • templateId · string · Required
  • voices · array · Required

Triggers

New Generated Video · Poll

Triggers when a new generated video appears in your Vidnoz account.

Inputs

  • limit · number
  • status · string

Setup

Setup

  1. Add the Vidnoz 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-vidnoz@0.0.8; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 2 actions and 1 trigger 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.
  • Runtime execution evidence is managed separately from package metadata.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Vidnoz 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-vidnoz@0.0.8 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