Connection / OAuth
The Connection field lets respondents authorize access to a third-party service directly within your form. When a respondent reaches this field, they see a button to connect their account via OAuth -- they click it, sign in to the service, grant permissions, and return to the form with a valid authorization token stored in the submission.
How it works
- You add a Connection field to your form and select which service to connect (e.g., Google, Slack, HubSpot)
- The respondent sees a "Connect [Service]" button in the form
- Clicking the button opens the service's OAuth consent screen in a new window
- The respondent signs in and grants the requested permissions
- The window closes and the form shows a "Connected" confirmation
- The authorization token is stored with the submission data
Supported services
Connection fields work with any integration that has been configured in your workspace's App Authorizations. Common services include Google (Gmail, Sheets, Calendar), Slack, HubSpot, Salesforce, and other OAuth-based integrations available in TinyCommand.
Configuration
| Setting | Description |
|---|---|
| Service | Which third-party integration to connect |
| Permissions scope | What access level to request from the user |
| Button text | Custom label for the connect button (default: "Connect [Service]") |
| Required | Whether the respondent must connect before proceeding |
What gets stored
The submission data includes the authorization token and connection metadata -- not the respondent's password. This token can then be used in downstream workflow nodes to act on behalf of the respondent (send emails from their account, read their spreadsheets, post to their Slack).
Using in workflows
When connected to a workflow via the Form Submission trigger, the connection token is available as a variable:
{{trigger.connectionFieldName}}
Use it in downstream nodes to perform actions using the respondent's authorized account -- for example, sending a message to their Slack workspace or creating a row in their Google Sheet.
When to use
- Onboarding flows -- connect a new user's tools during signup
- Integration setup -- let users authorize services as part of a configuration form
- Data import -- authorize access to pull data from the user's accounts