Skip to content
All connectors
Typeform logo

Typeform

Marketing & advertising

Turn orders and customer changes into the right Typeform audiences and campaigns, with a person approving what goes out.

15 ways to read, 7 ways to write, each write switched on by you.

Quality checks

Built and tested with example responses.

  1. Ready to connect: doneEvery listed action is built in.
  2. Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Typeform with Nexra

Connected, approved, proven.

The things teams do most with Typeform, an example flow with a person in the loop, and what Nexra keeps as proof.

Top actions

  • Create formApproval by rule
  • Create themeApproval by rule
  • List account workspacesRead

Example flow

  1. Typeform · List account workspacesDone
  2. Typeform · Create formNeeds approval
  3. Nexra · Record the decision and result in the evidence chainProven

Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Typeform.

What gets logged

  • Whether it ran on its own or who approved it, and under which rule
  • A fingerprint of the exact request sent to Typeform
  • Typeform's reply: what it created or changed
  • One entry in the evidence chain, linked to the one before

Try this in the sandbox

Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.

For developers

Technical detail

Read Typeform forms, responses, images, themes, workspaces, members and webhooks; manage forms, form messages, themes and workspaces.

Typeform API docs
Source actions
15
Destination actions
7
Data types
10

What you can map

Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.

Account workspaces1
  • List account workspacesSource

    Workspaces you can access within one Typeform account (organisation).

Account1
  • Get own accountSource

    The token owner's Typeform alias, email address and language.

Form messages2
  • Get form messagesSource

    Customised button labels, errors and other messages for a form.

  • Update form messagesDestinationProvider duplicate protectionApproval before production

    Replaces a form's customised messages, such as button labels and error texts. Bold and italic markup is allowed; HTML is not.

Forms4
  • Create formDestinationNot retried automaticallyApproval before production

    Creates a form from a title and an optional Typeform field definition.

  • Get formSource

    A form with its questions, choices, hidden fields, variables and settings.

  • List formsSource

    Forms in the account, optionally in one workspace, newest updates first.

  • Update form settingsDestinationProvider duplicate protectionApproval before production

    Changes a form's title, public visibility, theme or workspace (JSON Patch).

Images2
  • Get imageSource

    An image's JSON description: size, media type and average colour.

  • List imagesSource

    Images in the Typeform account, newest first.

Responses1
  • List responsesSourceIncremental

    Form responses with answers keyed by field ref, newest first, filtered by submission time and completion.

Themes4
  • Create themeDestinationNot retried automaticallyApproval before production

    Creates a private theme with colours, font, alignment and an optional background image.

  • Get themeSource

    One theme's font, colours and background.

  • List themesSource

    Public and private themes available to the account.

  • Update themeDestinationProvider duplicate protectionApproval before production

    Changes the supplied parts of a private theme (partial update). Colours, question and screen settings are each replaced as a group.

Webhooks2
  • Get form webhookSource

    One webhook on a form by its tag.

  • List form webhooksSource

    Webhooks configured on a form. Signing secrets are not returned.

Workspace members1
  • List workspace membersSource

    People with access to a workspace and their role. Read-only.

Workspaces4
  • Create workspaceDestinationNot retried automaticallyApproval before production

    Creates a workspace to group forms.

  • Get workspaceSource

    One workspace with its members.

  • List workspacesSource

    Workspaces in the account with form counts.

  • Rename workspaceDestinationProvider duplicate protectionApproval before production

    Renames a workspace (JSON Patch on /name).

Access and limits

Authentication
Personal access token
Plans and access
All Typeform plans, including free. Personal access tokens carry the scopes chosen when they are created. EU data centre accounts use the EU API origin.
Test environment
Use a free Typeform account with a test form.
Rate limits
Two requests per second per Typeform account for the Create and Responses APIs; HTTP 429 with backoff.
Pagination
Page numbers with page_count for forms, workspaces and themes; responses page backwards with the before token of the last response.
Provider events
Typeform webhooks (form_response events, signed with HMAC SHA-256). Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.

Before you build a flow

  • Deleting forms, responses, workspaces, themes, images and webhooks is intentionally not implemented.
  • Image upload is not implemented; images are read-only and image get returns the JSON description, never the binary.
  • Theme creation has no idempotency key; uncertain creates are not repeated automatically. Theme colours, question settings and screen settings are each sent as a complete group, as Typeform requires.
  • Account information comes from GET /me (alias, email, language); OAuth tokens need the accounts:read scope.
  • Full form replacement (PUT /forms/{id}) is not implemented because it deletes questions and their responses that are not in the new definition; form updates use JSON Patch on title, visibility, theme and workspace only.
  • Webhook creation and changes are not implemented; webhooks and their configuration are read-only and signing secrets are never returned.
  • Response search (query) is not exposed because the search text would travel in the URL query string.
  • Workspace member changes are not implemented because they send invitations.
  • Form and workspace creation have no idempotency key; uncertain creates are not repeated automatically.
  • Files uploaded in responses are returned as Typeform file URLs; file contents are not downloaded.

Developer reference

  1. Create the Typeform credentials described above with the narrowest permissions your flows need.
  2. In Nexra, open Connect, then Connections, then New connection, choose Typeform, enter its settings and credentials, and tick only the write actions you need. Connection guide
  3. Test the connection, then use its actions as flow sources and destinations. Flow guide

Machine-readable detail: GET /api/public/connect/connectors/typeform and the Connections API.