Formstack
Read Formstack forms, fields and folders, and list, search, create and delete submissions — on the V2025 API.
About
Formstack ships in the w6w first-party pack. It declares 9 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.formstack- Version
- 0.1.4
- Author
- w6w
- Licence
- MIT
- Categories
- Forms & Surveys · Productivity
Overview
Formstack manages forms, fields, folders and submissions through the Formstack V2025 API, giving a workflow read access to a form’s structure and full control over the submissions built against it. Forms and their field definitions are listed and read first, since a submission is keyed by field id — the same ids a workflow needs both to write a new submission and to make sense of one read back.
Reading submissions defaults to returning parsed field values rather than just metadata, since the answers are what most workflows actually want and Formstack only includes them when explicitly asked. New submissions are always sent as JSON, because Formstack’s default form-encoded format can’t carry structured field values like checkboxes and matrix questions intact. Deleting a submission is permanent — Formstack removes it and any attached files with no way to recover it.
Building and editing forms themselves — fields, confirmation emails, smart lists — is left to Formstack’s own design-time UI rather than this integration, which stays focused on submission data.
Build with Formstack
Three routes to the same 9 actions. The Workflow tab is generated from Formstack'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 Fields
form-fields List a form's fields — id, type, label and whether each is required. Read this before creating a submission.
Create Submission
submission-create Submit an entry to a form. Field values are keyed by field id, not by label.
Delete Submission
submission-delete Permanently delete a submission and all of its associated data, including uploaded files. There is no undo.
List Submissions
submission-list List a form's submissions. Field answers are included by default — without them a submission is only metadata.
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 Formstack's real ids.
{
"manifestVersion": "2",
"name": "formstack-example",
"steps": [
{
"id": "form-fields",
"uses": {
"app": "io.w6w.formstack",
"action": "form-fields",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"formId": "<formId>"
}
}
]
}Here are some of the things you can do
-
List Form Fields
searchform-fields -
List Folders
searchfolder-list -
Get Form
readform-get -
List Forms
searchform-list -
Count Submissions
readsubmission-count
+4 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 Formstack, 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 Formstack. 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: "submission-create",
payload: {
formId: "<value>",
fields: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action submission-create --payload '{"formId":"<value>","fields":"<value>"}'Give an AI agent Formstack — without giving it Formstack'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.formstack#form-fields",
"input": {
"formId": "<formId>"
}
}
}
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 Formstack 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
Formstack'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. Formstack itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Formstack declares its own checks, so its health is a property of the app rather than something the host guesses at.
Intellistack platform status
Component status from www.intellistackstatus.com — the status page for Intellistack, the parent brand Formstack is now part of. It covers the whole portfolio, so it is informational rather than evidence about this connection.