Mattering Automations Typeform integration
Connect Typeform to Mattering Automations: forms, responses with filters, workspaces, themes, and per-form webhooks as workflow steps, authenticated with a Typeform Personal Access Token.
The Mattering Automations Typeform integration adds Typeform to your automation canvas: list and read forms, pull responses with time windows and filters, create and edit forms, organize workspaces, apply themes, and manage each form's webhooks.
Setup takes a couple of minutes: generate a Personal Access Token in your Typeform account, attach it as a credential in Mattering, and test the connection. This guide walks through each step and ends with the full node reference.
One rule keeps Typeform automation safe: know which update you are making. Typeform: Patch Form handles the safe edits (title, settings, theme, workspace) and cannot touch fields. Changing fields or logic requires Typeform: Overwrite Form (PUT), a full replacement where Typeform deletes any field omitted from the body along with its response data, so the fixed recipe is fetch the definition, modify it, send the whole thing back. Typeform: Delete Form likewise removes the form and all of its responses in one call.
Before you start
- A Typeform account with at least one form (any plan; the API works on the free tier).
- Permission to create a Personal Access Token under Settings, then Personal tokens.
- A Mattering workspace with access to the Automations app.
- Not supported: Enterprise EU data center accounts (api.eu.typeform.com uses region-unique tokens; this integration targets the default api.typeform.com).
Create a Typeform Personal Access Token
Mattering authenticates to Typeform with a Personal Access Token, sent as a bearer credential on every request. You choose the token's scopes when creating it.
Connect Typeform to Mattering
Verify it works
After connecting, open any automation canvas and check the palette: a Typeform section should list the query and action nodes. Drop Typeform: List Forms onto the canvas and run a test step: it is a safe read, and a successful response lists your forms with the form ids the response and webhook nodes ask for.
Then run Typeform: List Responses with a form id from the first step to confirm response access end to end, and Typeform: Get Form to see a full form definition, which is also the fastest way to learn the shape Typeform: Create Form expects. Everything in this path is read-only.
Node reference
22 nodes, generated from the connector itself so this reference always matches what ships.
Read and query nodes 10
Typeform: Get Form
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
typeform_get_me
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
typeform_get_theme
Retrieve one theme by id: colors, font, background, field and screen styling, and visibility.
Typeform: Get Webhook
typeform_get_webhook
Retrieve one webhook on a form by its tag: destination URL, enabled state, event types, and timestamps.
Typeform: Get Workspace
typeform_get_workspace
Retrieve one workspace by id: name, share status, member list, and form count.
Typeform: List Forms
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
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
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
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
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
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
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
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
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
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
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
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
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
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)
typeform_update_form
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
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
typeform_update_workspace
Rename a workspace or add/remove members with JSON Patch style operations. Returns 204 on success.
Using the integration
On the automation canvas
Typeform nodes chain with every other node: a scheduled Typeform: List Responses sweep with a since filter can file each new submission as a task in Mattering Productivity or a record in a Mattering database, an AI step can summarize the answers on the way through, and urgent submissions can branch to a priority queue.
From AI assistants over MCP
Every node speaks MCP, the open protocol for connecting AI assistants to tools. Claude, ChatGPT, and Matter can list forms, read definitions, and pull responses through the same nodes your workflows use. The read surface is the safe majority of the connector; the destructive nodes are clearly flagged for agent use too.
Two update paths with different blast radii
Typeform: Patch Form applies targeted RFC 6902 operations to a fixed set of paths (title, several settings, theme, workspace) and leaves everything else alone; it is the safe path for renames and moves, and it cannot touch fields or logic. Field and logic changes go through Typeform: Overwrite Form (PUT), a full replacement where Typeform documents that omitted fields are deleted along with their associated response data. The safe overwrite recipe never varies: Typeform: Get Form, modify that JSON, send the entire definition back.
Response sweeps that stay incremental
Typeform: List Responses supports since and until windows, completion filters, free-text search, field filters, and cursor pagination. The standard sweep pattern: persist the last run time, pass it as since, and each run processes only new submissions. File-upload answers arrive as file_url values that download with the same bearer token; raw bytes never enter the workflow.
Templated form creation
Typeform: Create Form takes a complete definition as one JSON object, which suits templating: keep a working definition (captured via Typeform: Get Form) as the base, vary titles, fields, and the target workspace per client or campaign, and create. Typeform: Create Theme and the workspace nodes keep branding and organization consistent.
Webhooks by tag, honestly labeled
Typeform: Create or Update Webhook sets a form's webhook under a tag you choose (PUT by tag, so re-running with the same tag updates in place), and Typeform: List Webhooks, Typeform: Get Webhook, and Typeform: Delete Webhook manage the rest. Management only: there is no inbound Typeform trigger in this integration, but the webhooks you configure can point at any URL you operate.
Troubleshooting
Test Connection fails with a 401
Test Connection passes but a node returns a 403
Everything fails with 404s for an EU account
A form update removed fields I did not touch
Response sweeps return duplicates or miss submissions
Delete Responses returned 200 but responses still appear
A file answer's URL will not download outside the workflow
Create Form rejects a definition
Related
The Typeform MCP
What connecting Typeform unlocks for AI agents and automations, with common uses and FAQs.
More guides
All Automations documentation
Every integration guide, plus how connectors, credentials, and workflows fit together.
Typeform is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.