Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

VideoAsk

VideoAsk integration for Flows360 workflows.

CategoryForms And Surveys
AuthenticationOAuth 2.0
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 24, 2026

Overview

Connect VideoAsk with Flows360

VideoAsk integration for Flows360 workflows.

Use the VideoAsk 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 4 triggers.

Available actions

  • Add tag to contact
  • create contact
  • Remove tag from contact
  • Search form by keyword(s)
  • Update contact
  • Custom API Call

Available triggers

  • Form contact message
  • Form transcribed
  • new form response
  • New form author response

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: VideoAsk
  • Package: @activepieces/piece-videoask@0.2.0
  • Exact artifact digest: sha256:af43d2c03ddf5c5644b7fca14721f8d05289923a3a06a88a1ad8823fe48ee8b8
  • 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

  • Add tag to contact (addTagToContact), Add a tag to a contact (respondent) in VideoAsk Classification: read.
  • create contact (createContact), Create a new respondent (contact) Classification: read.
  • Remove tag from contact (removeTagFromContact), Remove a tag from a contact (respondent) in VideoAsk Classification: read.
  • Search form by keyword(s) (searchForm), Search forms by keyword(s) within the organization Classification: read.
  • Update contact (updateContact), Update an existing respondent (contact) in VideoAsk Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • Form contact message, webhook.
  • Form transcribed, webhook.
  • new form response, webhook.
  • New form author response, webhook.

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 objects10
Supported actions6
Triggers4

Authentication

Authentication method: OAuth 2.0

Authentication profiles

connection · oauth2

Supported objects

ObjectReadWriteNotes
Add tag to contact Yes No Add a tag to a contact (respondent) in VideoAsk
create contact Yes No Create a new respondent (contact)
Remove tag from contact Yes No Remove a tag from a contact (respondent) in VideoAsk
Search form by keyword(s) Yes No Search forms by keyword(s) within the organization
Update contact Yes No Update an existing respondent (contact) in VideoAsk
Custom API Call Yes No Make a custom API call to a specific endpoint
Form contact message Yes No webhook trigger declared by the pinned package.
Form transcribed Yes No webhook trigger declared by the pinned package.
new form response Yes No webhook trigger declared by the pinned package.
New form author response Yes No webhook trigger declared by the pinned package.

Supported actions

Add tag to contact · Read

Add a tag to a contact (respondent) in VideoAsk

add_tag_to_contact · Risk: low · Retry: safe

Inputs

  • organizationId · string · Required, Select the organization
  • contactId · string · Required, The contact (respondent) id to add the tag to
  • tagId · string · Required, Select the tag
create contact · Read

Create a new respondent (contact)

create_contact · Risk: low · Retry: safe

Inputs

  • organizationId · string · Required, Select the organization
  • name · string · Optional, The name of the contact
  • email · string · Required, The email of the contact
  • phone_number · string · Optional, The phone number of the contact
Remove tag from contact · Read

Remove a tag from a contact (respondent) in VideoAsk

remove_tag_from_contact · Risk: low · Retry: safe

Inputs

  • organizationId · string · Required, Select the organization
  • contactId · string · Required, The contact (respondent) id to remove the tag from
  • tagId · string · Required, Select the tag
Search form by keyword(s) · Read

Search forms by keyword(s) within the organization

search_form · Risk: low · Retry: safe

Inputs

  • organizationId · string · Required, Select the organization
  • limit · number · Optional, Maximum number of results to return
  • search · string · Required, Keyword(s) to search for in form titles
Update contact · Read

Update an existing respondent (contact) in VideoAsk

update_contact · Risk: low · Retry: safe

Inputs

  • organizationId · string · Required, Select the organization
  • respondentId · string · Required, The ID of the respondent to update
  • name · string · Optional, The name of the contact
  • email · string · Optional, The email of the contact
  • phone_number · string · Optional, The phone number of the contact
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.
  • organizationId · string · Required, Select the organization

Triggers

Form contact message · Webhook

Triggers when a contact sends a message via a form

Inputs

  • organizationId · string
  • formId · string
  • tag · string
Form transcribed · Webhook

Triggered when a form is transcribed

Inputs

  • organizationId · string
  • formId · string
  • tag · string
new form response · Webhook

Trigger when a new form response is submitted

Inputs

  • organizationId · string
  • formId · string
  • tag · string
New form author response · Webhook

Trigger when a form author responds to a contact message

Inputs

  • organizationId · string
  • formId · string
  • tag · string

Setup

Setup

  1. Add the VideoAsk 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-videoask@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 6 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 VideoAsk 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-videoask@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