Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

VidLab7

AI Avatars that pitch, show demos, qualify buyers, follow up, secure meetings and close deals – on autopilot.

CategoryArtificial Intelligence
Authenticationcustom
Version0.1.7
Published scopes0 published scopes
Last updatedSeptember 24, 2026

Overview

Connect VidLab7 with Flows360

AI Avatars that pitch, show demos, qualify buyers, follow up, secure meetings and close deals – on autopilot.

Use the VidLab7 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 1 action and no declared triggers.

Available actions

  • Create Video

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: VidLab7
  • Package: @activepieces/piece-vidlab7@0.1.7
  • Exact artifact digest: sha256:23843c278f8423087eee1b309f932d17d08b36853a34ad82d4b6002ed4b3e0ad
  • 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

  • Create Video (createVideo), Generate a video using a studio avatar 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 objects1
Supported actions1
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Video Yes No Generate a video using a studio avatar

Supported actions

Create Video · Read

Generate a video using a studio avatar

create_video · Risk: low · Retry: safe

Inputs

  • avatarId · string · Required, The ID of the avatar to be used for the video generation
  • script · string · Required, The script to be used for the video generation
  • voiceId · string · Required, The ID of the voice to be used for the video generation
  • webhookUrl · string · Required, The URL to which the webhook will be sent when video generation is complete
  • similarity_boost · number · Optional, Voice similarity boost setting (0-100)
  • use_speaker_boost · boolean · Optional, Enable speaker boost for better voice quality
  • style · number · Optional, Voice style setting
  • stability · number · Optional, Voice stability setting (0-100)
  • waitForCompletion · boolean · Optional, Wait for the video generation to complete and return the video URL. If disabled, only returns the video ID.

Setup

Setup

  1. Add the VidLab7 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-vidlab7@0.1.7; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 1 action 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 VidLab7 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-vidlab7@0.1.7 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