Wufoo
Read Wufoo forms, fields, entries and reports, and submit new entries — with the entry filters, sorting and paging the v3 API provides.
About
Wufoo 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.wufoo- Version
- 0.1.3
- Author
- w6w
- Licence
- MIT
- Categories
- Forms & Surveys · Productivity
Overview
Wufoo puts form data into a workflow — list an account’s forms, read one form’s fields and identifiers, list entries with structured filters, count entries, submit a new entry, and read saved reports and the entries behind them. Every field on a form is addressed by a stable id rather than its label, so a workflow starts by reading a form’s fields once and reuses those ids for filtering and submitting.
Wufoo answers a rejected entry submission with an HTTP 200 carrying a per-field error list rather than a failure status, so this app reads that success flag directly instead of trusting the status code — the most damaging way to misuse this API is to treat a 200 as proof the entry was accepted. Filters use a closed set of vendor-defined operators; a misspelt one silently returns an empty result rather than an error, so the app validates against the real list before sending the request, and every date filter is interpreted in Pacific time regardless of what timezone a workflow is running in.
One documented endpoint is deliberately never called: it returns every user’s credential on the account, not just the caller’s, so this app has no user-listing action and its connection label is built from the account subdomain instead.
Build with Wufoo
Three routes to the same 8 actions. The Workflow tab is generated from Wufoo'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.
Create Entry
entry-create Submit an entry to a form. Fields are keyed by id (`Field105`), not by label — Wufoo reports a validation failure as HTTP 200, which this action turns into a real error.
List Form Entries
entry-list List a form's submissions, with Wufoo's filters, sorting and paging. Filter dates are interpreted in Pacific time.
List Form Fields
form-fields List a form's fields — their `ID` (`Field105`), type, whether they are required, and any choices. Read this before submitting an entry.
List Forms
form-list List every form on the account. Start here — the `Hash` on each form is what the other actions take.
List Report Entries
report-entries List the entries a saved report returns. The report's own filters apply — use List Form Entries for ad-hoc filtering.
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 Wufoo's real ids.
{
"manifestVersion": "2",
"name": "wufoo-example",
"steps": [
{
"id": "entry-count",
"uses": {
"app": "io.w6w.wufoo",
"action": "entry-count",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"identifier": "<identifier>"
}
}
]
}Here are some of the things you can do
-
Count Form Entries
readentry-count -
Create Entry
performentry-create -
List Form Entries
searchentry-list -
List Form Fields
searchform-fields -
Get Form
readform-get
+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 Wufoo, 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 Wufoo. 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: "entry-create",
payload: {
identifier: "<value>",
fields: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action entry-create --payload '{"identifier":"<value>","fields":"<value>"}'Give an AI agent Wufoo — without giving it Wufoo'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.wufoo#entry-count",
"input": {
"identifier": "<identifier>"
}
}
}
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 Wufoo 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
Wufoo'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. Wufoo itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Wufoo declares its own checks, so its health is a property of the app rather than something the host guesses at.
Wufoo platform status
Page-level status from status.wufoo.com (Atlassian Statuspage). Wufoo publishes no per-component detail, so the page indicator is the whole signal.