VideoAsk
Create and manage VideoAsk forms, questions, respondents and their asynchronous video/audio/text conversations.
About
VideoAsk ships in the w6w first-party pack. It declares 38 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.videoask- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Forms & Surveys · Video & Streaming · Communication
Overview
VideoAsk (by Typeform) turns a form into an asynchronous video, audio or text conversation: a form has questions, a contact (aka respondent) answers them, and the exchange of answers and replies is a conversation over the REST API at api.videoask.com.
This app covers the lifecycle a workflow needs: list, search, create, update, duplicate, restore and delete forms; read a form’s metrics; read and create questions (an external media URL only — direct video/audio upload is a two-step, S3-presigned-POST flow this app does not attempt); filter a form’s conversations and read a single contact’s answers and messages; read a question’s answers and aggregate insights; create, update and delete respondents (contacts); read a video/audio’s transcript and edit its captions; manage tags, including attaching/detaching one to a contact; manage per-form webhooks; list an account’s organizations and brands; and read the connected account’s own profile.
Every request that isn’t organization-scoped by nature accepts an optional organization-id, because VideoAsk documents most endpoints as reachable across any organization the caller belongs to, not just their default one.
Build with VideoAsk
Three routes to the same 38 actions. The Workflow tab is generated from VideoAsk's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Delete Response
contact-delete Permanently delete a contact's response (answers and messages) to a form.
Get Contact
contact-get Fetch a single contact's record, with its answers and messages. Rate-limited by the vendor to 50 requests per 5 minutes.
Filter Responses
conversation-list List a form's contacts (respondents), filtered by read state, tag, score or date.
Get Form Metrics
form-metrics-get Read a form's landed/interacted/answered/completed totals and per-interval breakdown.
Search Forms
form-search Search form titles by keyword. Results are oldest-first, unlike List Forms.
Update Form
form-update Partially update a form. Common fields are typed; use Body (JSON) for anything else VideoAsk's form schema supports (e.g. metadata.*, requires_contact_*, close-date fields).
List Question Answers
question-answers-list List every answer given to one question. Returns a bare array, not a page envelope.
Create Question (External Media)
question-create Add a step to a form using an externally-hosted video or audio URL. Direct file upload is not supported by this app — host the media yourself first.
Duplicate Question
question-duplicate Duplicate a question within its form. The copy is not wired into the flow — connect it with a logic action via Update Question.
Get Question Insights
question-insights-get Read a question's aggregate stats (answer count, and poll option tallies if any).
Update Question
question-update Partially update a question. Common media fields are typed; use Body (JSON) for anything else, e.g. {"metadata": {"text": "…"}} for the on-screen script.
Create or Update Webhook
webhook-upsert Create a webhook (choose a new tag) or update an existing one (reuse its tag). Idempotent by design — a PUT with the same body has no further effect.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying VideoAsk's real ids.
{
"manifestVersion": "2",
"name": "videoask-example",
"steps": [
{
"id": "branding-get",
"uses": {
"app": "io.w6w.videoask",
"action": "branding-get",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"brandingId": "<brandingId>"
}
}
]
}Here are some of the things you can do
-
Get Brand
readbranding-get -
Get Account
readaccount-get -
List Brands
readbranding-list -
Get Contact
readcontact-get -
Add/Remove Contact Tag
performcontact-tag-set
+33 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for VideoAsk, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to VideoAsk. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "branding-get",
payload: {
brandingId: "<value>",
// organizationId: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action branding-get --payload '{"brandingId":"<value>"}'Give an AI agent VideoAsk — without giving it VideoAsk's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.videoask#branding-get",
"input": {
"brandingId": "<brandingId>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's VideoAsk connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
VideoAsk's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. VideoAsk itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
VideoAsk declares its own checks, so its health is a property of the app rather than something the host guesses at.
VideoAsk platform status
Component status from status.videoask.com: API, Website/Web App, Auth0 Authentication API and Subscriptions, plus the AWS regional and iOS App dependencies VideoAsk itself reports.