Integration reference

Typeform Trigger and Action reference

Start Workflows from submitted forms, retrieve responses, and create or update forms.

3 Triggers5 ActionsManifests: Trigger v1 · Action v1

Authentication

Connect your Typeform account through OAuth, then choose the forms whose responses FastHook should receive.

  • Trigger account type: oauth2; reconnect by oauth.
  • Action connection type: oauth2; available modes: Connected Typeform account.

Create or reuse the account from a Trigger or Action dialog, or manage it under Settings → Connected accounts. See Authentication and permissions for scopes and access diagnostics, or Connected accounts for reuse, reconnect, revocation, and credential rotation.

Scopes and permissions

Base Trigger authorization requests: accounts:read, forms:read, forms:write, responses:read, webhooks:read, webhooks:write, offline.

Operation-specific requirements appear in the tables below. Custom event selections can add scopes dynamically, so the current Trigger or Action dialog remains authoritative for the exact consent request.

Use Typeform as a Trigger

The current provider manifest contains 3 available Trigger definitions. Representative definitions include:

  • Form Response
View all 3 available Trigger definitions
TriggerManifest keyDeliveryAdditional scopes
Form Responsetypeform.form_response.instantinstantNone declared
Any Typeform Eventstypeform.any_event.instantinstantNone declared
Custom Typeform Eventstypeform.custom_webhook_events.instantinstantNone declared

Choose the narrowest event definition that fits the Workflow. Configure provider-specific resource and event filters in the Source dialog before adding broader Workflow Filters.

Use Typeform Actions

The current Action manifest contains 5 operations. Representative Actions include:

  • Get Form
  • List Responses
  • Create Form
  • Update Form
View all 5 available Action definitions
ActionManifest keyAccess and authManifest rate limit
Get Formtypeform.get_formNone declared
FastHook-managed account
1/second
List Responsestypeform.list_responsesNone declared
FastHook-managed account
1/second
Create Formtypeform.create_formNone declared
FastHook-managed account
1/second
Update Formtypeform.update_formNone declared
FastHook-managed account
1/second
Custom API Requesttypeform.custom_api_requestNone declared
FastHook-managed account
1/second

The Action editor reads its required permissions, fields, remote resource pickers, output schema, and rate limit from the provider manifest. Available fields can change with the selected operation and authentication mode.

Build a Workflow

  1. Create a Source using a Typeform Trigger definition.
  2. Create a Workflow with that Source as its Trigger.
  3. Add the required Typeform Action and select the connected account.
  4. Map Trigger or earlier-Step data into the Action fields with the field picker.
  5. Add a Filter, Paths, Delay, or Transformation when the route needs it.
  6. Activate the Workflow, produce a controlled event, and verify the run in Audit and in Typeform.

Troubleshooting Typeform

The account is missing or cannot be selected
Confirm the active FastHook team, provider, account status, and authentication mode. A disabled or revoked account cannot execute an Action.
A resource picker is empty
Verify that the connected provider identity can access the resource itself. OAuth consent does not add workspace, repository, channel, drive, project, base, or record permissions.
The editor asks for additional scopes
Reconnect the same account from the affected Trigger or Action so FastHook can request its current manifest scopes. Then reopen the editor and select the resource again.
An active Workflow returns 401, 403, or a permission error
Compare the selected operation’s access requirements below with the account recorded in Audit. Check provider-side membership and object access before repeating the Action.
The provider returns 429 or a temporary 5xx
Inspect the Step attempt and retryability in Audit. FastHook can retry temporary failures, but provider quotas and idempotency rules still apply.

Provider-specific checks

  • Update Form replaces the complete form definition. Include every existing field and its original ID to preserve fields and their results.
  • Webhook and response schemas use official examples; question types and answer fields vary by form.
  • FastHook manages form webhooks and verifies Typeform signatures over the original request body.

Next