Youform
Read Youform forms and submissions, manage submission webhooks and enable submission refill links.
About
Youform ships in the w6w first-party pack. It declares 7 actions, 3 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.youform- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Forms & Surveys
Overview
Youform is a form and survey builder with a deliberately small developer API, and this app covers all of it: the account profile, the list of forms, a single form’s definition, the submissions collected by a form, the webhooks that push submissions to another system, and the refill link that lets a respondent reopen a submission.
It can list completed and partial submissions with sorting and page size, read a form’s block definition so submission answers (keyed by block id) can be mapped back to question titles, register a webhook for a form and remove it again, and switch a submission’s refill link on or off.
Good for pulling new form answers into a CRM or sheet on a schedule, wiring a form to a workflow through a webhook subscription, following up on abandoned partial submissions, and sending a respondent their refill link to correct an answer. Youform’s API cannot create or edit forms, so this app does not either.
Build with Youform
Three routes to the same 7 actions. The Workflow tab is generated from Youform'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.
List submissions
submission-list List a form's submissions, completed, partial or both, newest or oldest first.
Set submission refill link
submission-refill-link-set Enable or disable the refill link that lets a respondent edit a submission.
Create webhook
webhook-create Register a webhook that Youform POSTs each new submission of a form to.
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 Youform's real ids.
{
"manifestVersion": "2",
"name": "youform-example",
"steps": [
{
"id": "form-get",
"uses": {
"app": "io.w6w.youform",
"action": "form-get",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"form": "<form>"
}
}
]
}Here are some of the things you can do
-
Get form
readform-get -
Get account
readaccount-get -
List forms
searchform-list -
List submissions
searchsubmission-list -
Set submission refill link
performsubmission-refill-link-set
+2 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 Youform, 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 Youform. 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: "form-get",
payload: {
form: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action form-get --payload '{"form":"<value>"}'Give an AI agent Youform — without giving it Youform'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.youform#form-get",
"input": {
"form": "<form>"
}
}
}
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 Youform 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
Youform'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. Youform itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Youform declares its own checks, so its health is a property of the app rather than something the host guesses at.
Youform API reachable
Unauthenticated GET https://app.youform.com/api/me. A 401 {"message":"Unauthenticated."} passes — it proves the API is serving.