Formsite
Read Formsite forms, items and results, and manage result-completed webhooks.
About
Formsite ships in the w6w first-party pack. It declares 8 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.formsite- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Forms & Surveys
Overview
Formsite is an online form and survey builder, and its REST API is built around one job: getting submitted results out. This app lets a workflow list the forms on an account, read a form’s items (the question labels that give result data meaning), and pull results with the same filters the Formsite API offers — date and result-ID windows, a saved Results View, sorting, and per-item search by equals, contains, begins-with or ends-with.
For reacting to submissions instead of polling for them, the app manages Formsite’s result-completed webhooks: list the webhooks on a form, create or update one (with an optional handshake key your receiver can verify), and delete one by URL.
Formsite accounts live on numbered servers (fs1, fs2, and so on) and are addressed by a user directory, so a connection records both next to the access token. API access requires a Professional-level Formsite plan, and the API is limited to 50 calls per minute and 10,000 per day per account.
Build with Formsite
Three routes to the same 8 actions. The Workflow tab is generated from Formsite'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 Form Items
form-items-list List a form's items (questions). Match each item's `id` against result item ids to label result data.
List Results
result-list Get a form's submitted results, newest first by default. Use `afterId` or `afterDate` to fetch only what's new since the last run.
Search Results
result-search Find results whose answers match. `contains`, `begins` and `ends` only work on text items; multiple-choice and meta items support `equals` only (search by the choice's position number).
Create or Update Webhook
webhook-create Subscribe a URL to a form's result-completed event. If a webhook with that URL already exists it is updated. The URL receives the same data as List Results, plus `handshake_key` when one is set.
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 Formsite's real ids.
{
"manifestVersion": "2",
"name": "formsite-example",
"steps": [
{
"id": "form-get",
"uses": {
"app": "io.w6w.formsite",
"action": "form-get",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"formDir": "<formDir>"
}
}
]
}Here are some of the things you can do
-
Get Form
readform-get -
List Form Items
searchform-items-list -
List Forms
searchform-list -
List Results
searchresult-list -
Search Results
searchresult-search
+3 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 Formsite, 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 Formsite. 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: {
formDir: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action form-get --payload '{"formDir":"<value>"}'Give an AI agent Formsite — without giving it Formsite'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.formsite#form-get",
"input": {
"formDir": "<formDir>"
}
}
}
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 Formsite 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
Formsite'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. Formsite itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Formsite declares its own checks, so its health is a property of the app rather than something the host guesses at.
Formsite platform status
Account server reachable
Unauthenticated request to this connection's Formsite server. A 401 passes — it proves the API is serving; token validity is the `auth:*` check's job.