A Typeform MCP that knows which update deletes your data
Connect one Personal Access Token and Typeform becomes workflow steps: list and read forms, pull responses with filters, create and edit forms, and manage workspaces, themes, and webhooks. Typeform has two ways to update a form, and only one of them is safe; this connector flags the other one honestly.
What the Typeform MCP connector does
The Typeform connector for Mattering Automations is 22 nodes across the Create and Responses APIs: forms (list, get, create, patch, overwrite, delete), responses (list with time windows, completion filters, and search; delete), workspaces (full CRUD), themes (list, get, create, delete), per-form webhooks (list, get, create-or-update, delete), and the account endpoint that anchors the connection test.
Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. An assistant can pull last week's responses, summarize what people actually said, and read a form's structure before proposing edits, without anyone opening Typeform.
Because Mattering is a work platform rather than middleware, form data lands somewhere useful by default: a scheduled response sweep can file each new submission as a task or a record in a Mattering database, and the answers travel with it, so the follow-up happens where the team already works.
The sharp edge in this API is update semantics, and the connector refuses to hide it. Typeform: Patch Form applies targeted operations and touches only what you name. Typeform: Overwrite Form (PUT) replaces the whole definition, and Typeform's docs are explicit that fields omitted from the body are deleted along with their associated response data, so the node is flagged destructive. Same for Typeform: Delete Form, which removes the form and all of its responses in one call.
One connection, three surfaces
- Visual automations. Drag Typeform nodes onto the canvas and wire them to triggers, conditions, and other apps.
- AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
- The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.
Every Typeform node, ready to drop on the canvas
22 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.
Read and query nodes 10
Typeform: Get Form
Retrieve a form's full definition: fields, logic, settings, screens, hidden fields, theme and workspace references. This is also the JSON you start from when updating a form with the PUT node (fetch, modify, send back whole).
Typeform: Get My Account
Retrieve the account profile behind the access token: alias, email address, and language. Takes no parameters, so it doubles as the credential health check (200 means the token works, 401 means it does not).
Typeform: Get Theme
Retrieve one theme by id: colors, font, background, field and screen styling, and visibility.
Typeform: Get Webhook
Retrieve one webhook on a form by its tag: destination URL, enabled state, event types, and timestamps.
Typeform: Get Workspace
Retrieve one workspace by id: name, share status, member list, and form count.
Typeform: List Forms
List the forms on the account, paginated, with optional search and workspace filters. Each item carries the form id, title, timestamps, and links to the live form and its responses.
Typeform: List Responses
Retrieve a form's submitted responses with time-window, cursor, and content filters. Each item carries response_id, landed/submitted timestamps, hidden field values, metadata, and the answers array (typed per question). File-upload answers arrive as an authenticated file_url, never inline file content.
Typeform: List Themes
List the themes available to the account (public gallery themes and private ones), paginated. Theme ids plug into form definitions as a theme href.
Typeform: List Webhooks
List all webhooks configured on a form: tag, destination URL, enabled state, and SSL verification setting. Management view only; delivering webhook payloads INTO an automation is not part of this connector.
Typeform: List Workspaces
List the account's workspaces (the folders forms live in), paginated, with an optional name search. Each item carries the workspace id used by the form and workspace nodes.
Action nodes 12
Typeform: Create Form
Create a form from a full Create API definition JSON. The definition needs at least a title; fields, settings, screens, logic, hidden fields, workspace and theme are optional. Returns 201 with the created form (including its new id). Any images referenced must already exist in the account.
Typeform: Create Theme
Create a private theme from a theme definition JSON (name, font, colors, background, field and screen styling). Returns 201 with the new theme; reference it from forms as https://api.typeform.com/themes/<id>.
Typeform: Create Workspace
Create a new workspace to organize forms into. Returns 201 with the new workspace, including its id.
Typeform: Create or Update Webhook
Create a webhook on a form, or update the one with the same tag (PUT upsert). New webhooks must use an https URL, and the receiver must answer 2XX within 30 seconds or Typeform retries and eventually disables the hook. This node manages the configuration only; it does not receive the payloads.
Typeform: Delete Form
DESTRUCTIVE: permanently delete a form AND all of the responses it has collected. There is no undo. Returns 204 on success.
Typeform: Delete Responses
DESTRUCTIVE: permanently delete specific responses from a form. A 200 means the deletion request was registered; the actual removal is asynchronous, so verify afterwards with Typeform: List Responses. There is no undo.
Typeform: Delete Theme
DESTRUCTIVE: delete a private theme by id. Returns 204 on success. Only themes the account owns can be deleted, not public gallery themes.
Typeform: Delete Webhook
DESTRUCTIVE: delete a form's webhook by tag, stopping delivery permanently (recreate it with Create or Update Webhook if needed). Returns 204 on success.
Typeform: Delete Workspace
DESTRUCTIVE: delete a workspace by id. Returns 204 on success. Move or back up any forms you care about first; Typeform's docs do not spell out what happens to forms left inside.
Typeform: Overwrite Form (PUT)
DESTRUCTIVE full replacement of a form's definition. Typeform documents that any fields omitted from the request are deleted ALONG WITH THEIR RESPONSE DATA, so always start from Typeform: Get Form, modify that JSON, and send the whole thing back. For safe partial edits (title, settings, theme, workspace) use Typeform: Patch Form instead.
Typeform: Patch Form
Partially update a form with RFC 6902 JSON Patch operations. Only a fixed set of paths is patchable (title, several settings, theme, workspace); form fields and logic are NOT, those require the PUT node. Returns 204 on success. This is the safe way to rename a form or move it between workspaces.
Typeform: Update Workspace
Rename a workspace or add/remove members with JSON Patch style operations. Returns 204 on success.
Connecting Typeform takes one credential
Typeform issues Personal Access Tokens from your account settings (Settings, then Personal tokens). Choose the scopes the token needs when you create it; Mattering sends it as a bearer credential on every request. Tokens for the EU data center are region-specific; this connector targets the default api.typeform.com.
In Typeform, open Settings, then Personal tokens, and generate a token with the scopes your automations need.
In Mattering Automations, open Connectors, click Add Connector, choose Typeform, and create a credential with that token.
Click Test Connection. Mattering calls Typeform's account endpoint and confirms the token authenticates.
All 22 Typeform nodes appear in the canvas palette. Run Typeform: List Forms first: it returns the form ids that the response and webhook nodes ask for.
Common uses for the Typeform MCP
Responses that file themselves
Typeform: List Responses pulls submissions with since and until windows, completion filters, and text search. On a schedule, each new response can become a task in Mattering Productivity or a record in a Mattering database, with the answers attached, so nothing sits unread in a results tab.
Reading a form before touching it
Typeform: Get Form returns the full definition: fields, logic, and settings. An assistant reads it to answer what a form asks and where its logic branches, and a workflow reads it before patching, so edits are made against the real current structure.
Safe edits with patch, careful edits with overwrite
Typeform: Patch Form covers the safe routine edits: title, settings, theme, and workspace, and touches nothing else. Form fields and logic can only change through Typeform: Overwrite Form (PUT), which replaces the whole definition, so the safe recipe there is fixed: fetch with Typeform: Get Form, modify that JSON, and send the entire thing back, because omitted fields are deleted along with their response data.
Forms created from templates you control
Typeform: Create Form takes a complete form definition as JSON, which makes templated generation natural: keep a base definition in a Mattering database, adjust titles and fields per client or campaign, and create the form as a workflow step, landing it in the right workspace.
Workspaces and themes under automation control
The workspace nodes cover full CRUD for organizing forms per client or team, and the theme nodes let a workflow apply consistent branding. Both deletes are flagged destructive and belong behind conditions.
Webhooks managed per form
Typeform: Create or Update Webhook sets a form's webhook by tag, and the list, get, and delete nodes manage the rest. Management only, and the connector says so: there is no inbound Typeform trigger, but the webhooks you manage can point at any URL you operate, and scheduled response sweeps cover polling.
Example: Every new response becomes a triaged task, summarized by AI
Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.
Trigger: a schedule runs every hour.
Typeform: List Responses pulls submissions since the last run for the intake form.
An AI step summarizes each response's answers into a two-line brief.
A task is created in Mattering Productivity per response, carrying the brief and the full answers.
A condition routes urgent submissions, flagged by the AI step, to a priority list with a notification, while the rest land in the normal queue.
Typeform MCP questions, answered
What Typeform operations are supported?
22 nodes: forms (list, get, create, patch, overwrite, delete), responses (list with filters, delete), workspaces (list, get, create, update, delete), themes (list, get, create, delete), per-form webhooks (list, get, create-or-update, delete), and the account endpoint. Deliberately not shipped: the Insights summary endpoint (it survives only in legacy docs and its reference pages no longer exist, so it was not built on memory), the Images API (base64 upload bodies), and the EU data center hosts (Enterprise-only, region-unique tokens).
Does this work with Claude, ChatGPT, or other AI assistants?
Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively.
What is the difference between Patch Form and Overwrite Form?
Scope and blast radius. Typeform: Patch Form applies targeted operations to a fixed set of paths: title, settings, theme, and workspace, and cannot touch form fields or logic. Typeform: Overwrite Form (PUT) is the only way to change fields, and it replaces the entire definition: Typeform's docs state that fields omitted from the body are deleted along with their associated response data, which is why the connector flags it destructive. Use patch for the paths it covers; for field edits, always fetch the current definition with Typeform: Get Form, modify it, and send the whole thing back.
Can deleting a form really delete response data?
Yes, twice over. Typeform: Delete Form removes the form and all of its responses in one call, and Typeform: Overwrite Form (PUT) deletes the response data of any field omitted from the new definition. Both are flagged destructive; keep them behind conditions or manual runs, and export responses first if there is any doubt.
How does response filtering work?
Typeform: List Responses accepts since and until timestamps, a completion filter (submitted versus abandoned), free-text search across answers, and field-level filters, with cursor pagination via before and after. The practical pattern for sweeps: track the last run time and pass it as since, so each run processes only new submissions.
Can a Typeform submission trigger a workflow?
Not as a trigger node in this connector. The webhook nodes manage a form's webhook configuration rather than receiving events, so there is no inbound Typeform trigger. The honest pattern today is polling: run Typeform: List Responses on a schedule with a since filter. The webhooks you manage can still point Typeform's events at any URL you operate.
How do file upload answers come through?
As URLs, not bytes. When a form has a file upload field, the response's answer carries a file_url that downloads the file with the same bearer token the connector already holds. Raw file content never inflates workflow payloads, and downstream steps get a link they can fetch or store.
What does creating a form through the API involve?
Typeform: Create Form takes the full form definition as JSON: title, fields, logic, and settings, in Typeform's documented create shape. The connector deliberately models it as one definition object rather than exploding every property into separate fields, because real usage is templated: store a working definition, vary the parts that change, and send it. Typeform: Get Form on an existing form is the fastest way to learn the shape.
Put Typeform to work inside your workspace
Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.
All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Typeform is a product of its respective owner; Mattering is an independent platform.