Menu

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.

In Typeform, open Settings, then Personal tokens, and click to generate a new token.
Select the scopes your automations need: forms and responses scopes for the core flows, plus workspaces, themes, and webhooks scopes if those nodes will be used.
Copy the token (it is shown once).
An under-scoped token passes the connection test, which only reads your account profile, but returns permission errors on the surfaces it cannot touch. If a node fails with a 403 while the test passes, regenerate the token with the missing scope and update the credential.

Connect Typeform to Mattering

In Mattering Automations, open Connectors and click Add Connector.
Choose Typeform from the list.
Click Create new credential, paste your Personal Access Token, and save.
The credential is stored encrypted in Google Secret Manager and never appears in workflow logs.
Click Test Connection: Mattering calls Typeform's account endpoint and confirms the token authenticates.
Click Connect. All 22 Typeform nodes appear in your canvas palette.

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
The token is invalid, was revoked, or picked up stray whitespace when pasted. Generate a fresh Personal Access Token under Settings > Personal tokens and update the credential on the connector.
Test Connection passes but a node returns a 403
The token is under-scoped: the connection test only reads your account profile, so a token missing forms, responses, workspaces, themes, or webhooks scopes passes it while those nodes are refused. Scopes are fixed at creation; generate a new token with the right scopes and update the credential.
Everything fails with 404s for an EU account
Enterprise accounts on Typeform's EU data center live at api.eu.typeform.com with region-unique tokens, and this integration targets the default api.typeform.com. EU data center accounts are not supported by these nodes.
A form update removed fields I did not touch
The update ran through Typeform: Overwrite Form (PUT) with a partial body: PUT replaces the entire definition, and Typeform deletes any field omitted from it along with that field's response data. The lost response data is not recoverable through the API. Going forward: use Typeform: Patch Form for the edits it supports (title, settings, theme, workspace), and when fields must change, always start from Typeform: Get Form and send the complete modified definition back.
Response sweeps return duplicates or miss submissions
Check the since bookkeeping: pass the previous run's timestamp, not a fixed window, and page with the documented cursors when a run returns a full page. Also confirm the completion filter matches intent: submitted responses and abandoned ones are different populations, and the deprecated completed parameter has been superseded by response_type.
Delete Responses returned 200 but responses still appear
Response deletion is asynchronous on Typeform's side: the 200 acknowledges the request, and the actual removal completes shortly after. Re-query after a delay rather than treating an immediate follow-up read as proof of failure.
A file answer's URL will not download outside the workflow
file_url values on file-upload answers require the same bearer authentication the connector uses; they are not public links. Fetch the file within an authenticated step and store it somewhere durable if it needs to outlive the workflow run.
Create Form rejects a definition
The definition object must match Typeform's create shape: field types, properties, and logic references all validate server-side. The reliable path is to capture a working form with Typeform: Get Form, modify it minimally, and strip server-assigned ids where the create API rejects them. Validation errors name the offending path; fix that path rather than rebuilding blind.

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.

Start Free Explore our Products