Skip to main content

​
At a glance

  • Availability: Experimental (how to enable).
  • Authentication: OAuth 2.0.
  • Connection: A user authorizes the connection in the provider’s consent screen.
  • Scopes: accounts:read, forms:read, responses:read, workspaces:read, offline.
  • Provider documentation: Authentication reference.

​
Credentials

Set these per environment. See Connect an integration. These variables are required only when you supply your own OAuth app. If a managed app is available, you can connect without setting them. Provider permissions and consent still apply.

​
Setup

  1. Create a Typeform developer app: Sign in at https://admin.typeform.com, open your account settings, and register an OAuth application (free accounts can create apps for testing).
  2. Set the redirect URI: Add your deployment’s /api/auth/typeform/callback URL as the app’s redirect URI.
  3. Set environment variables: Copy the Client ID and Client Secret into TYPEFORM_CLIENT_ID and TYPEFORM_CLIENT_SECRET in your .env.
  4. Connect and verify: Complete the OAuth consent flow, then run Get Me and List Forms to confirm access.

​
Provider notes

  • The ‘offline’ scope is required to receive a refresh token; without it access expires and the user must reauthorize
  • Token requests send client_id and client_secret as URL-encoded form fields in the POST body
Provider API reference.

​
Tools

​
Verify the connection

Call a read tool such as typeform__list_forms with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.