Create and manage SurveyMonkey surveys, responses, collectors and contacts via the SurveyMonkey API.
SurveyMonkey ships in the w6w first-party pack. It declares 12 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
io.w6w.surveymonkeySurveyMonkey puts a survey program’s read side into a workflow — list and read surveys, pull a survey’s full page and question detail, create a new survey, read bulk survey responses and drill into one response’s detail, list and create collectors, list survey pages, and manage contact lists including adding a new contact.
Writing responses back into SurveyMonkey is deliberately left out: that scope needs the vendor’s own approval to use in a public app, and this pack has no case yet that needs it. Webhooks are likewise out of scope for an app that only performs actions, not triggers.
SurveyMonkey is one of the few vendors in this pack to publish live, real rate-limit headers rather than leaving quota undocumented — a draft or private app is capped at 120 requests per minute and 500 per day, shared across every connection made through this app rather than metered separately per connection.
Three routes to the same 12 actions. The Workflow tab is generated from SurveyMonkey'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.
collector-create Create a collector to distribute a survey (weblink, email, SMS or popup).
response-get-details Retrieve a single response, fully expanded with all question answers.
response-get-many Retrieve the full, answer-expanded responses submitted to a survey, with paging and filtering.
survey-create Create a SurveyMonkey survey, optionally from a template or an existing survey.
survey-get-many List surveys in the account, with optional search, folder filter and paging.
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 SurveyMonkey's real ids.
{
"manifestVersion": "2",
"name": "surveymonkey-example",
"steps": [
{
"id": "collector-create",
"uses": {
"app": "io.w6w.surveymonkey",
"action": "collector-create",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"surveyId": "<surveyId>",
"type": "<type>"
}
}
]
}collector-create collector-get-many contact-create contact-list-get-many page-get-many +7 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 SurveyMonkey, 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 SurveyMonkey. 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: "survey-create",
payload: {
// title: "<value>",
// nickname: "<value>",
// language: "<value>",
// folderId: "<value>",
// fromSurveyId: "<value>",
// fromTemplateId: "<value>",
// footer: "<value>",
// definition: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value); npm install -g @w6w/cli w6w run conn_YOUR_CONNECTION_ID --action survey-create --payload '{}' Give an AI agent SurveyMonkey — without giving it SurveyMonkey'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.surveymonkey#collector-create",
"input": {
"surveyId": "<surveyId>",
"type": "<type>"
}
}
}
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 SurveyMonkey connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
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.
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.
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.
SurveyMonkey'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. SurveyMonkey itself is MIT, and the runtime that executes it is source-available (FSL).
SurveyMonkey declares its own checks, so its health is a property of the app rather than something the host guesses at.
Atlassian Statuspage rollup for status.surveymonkey.com, with per-component detail. Unauthenticated and unsigned.
Per-minute and per-day allowances remaining, read off the `X-Ratelimit-App-Global-*` headers on a GET /users/me call.