Skip to main content

Authorization

Follow this guide to create a new Google Forms API credential that will allow Nexla to authenticate to and exchange data with your Google Forms account.
google_forms_api_auth.png

Google Forms API

Prerequisites​

Before creating a Google Forms API credential in Nexla, you must set up OAuth 2.0 authentication in Google Cloud Console. The Google Forms API uses OAuth 2.0 to authorize access to form data, requiring you to create a Google Cloud project, enable the Forms API, configure an OAuth consent screen, and obtain client credentials.

Google Cloud Project Setup​

To obtain the required OAuth 2.0 credentials for the Google Forms API:

  1. Sign in to Google Cloud Console: Navigate to https://console.cloud.google.com/ and sign in with your Google account. If you do not yet have a Google Cloud project, click Select a project at the top of the page, then click New Project to create one.

  2. Create or Select a Project: In the Google Cloud Console, select an existing project from the project dropdown at the top of the page, or click New Project to create a new one. Enter a descriptive project name (e.g., "Nexla Google Forms Integration") and click Create.

  3. Enable the Google Forms API: Navigate to APIs & Services > Library in the left navigation menu. Search for "Google Forms API" and click on the result. Click Enable to activate the API for your project.

    The Google Forms API must be enabled in your Google Cloud project before you can create credentials or make API calls. If the API is not enabled, all requests will return a 403 error.

  4. Configure the OAuth Consent Screen: Navigate to APIs & Services > OAuth consent screen in the left navigation menu. This screen defines how your application appears to users during the authorization process.

    1. Select the appropriate user type:

      • Internal — available only for Google Workspace organizations; limits access to users within your organization.
      • External — available to any Google account user; requires verification for production apps with more than 100 users.

    2. Click Create and fill in the required application information:

      • App name: Enter a descriptive name (e.g., "Nexla Forms Connector").
      • User support email: Enter your email address.
      • Developer contact information: Enter your email address.

    3. Click Save and Continue to proceed to the Scopes step.

    4. Click Add or Remove Scopes and add the following scopes based on your intended use:

      • https://www.googleapis.com/auth/forms.body — Read and write access to form structure and settings.
      • https://www.googleapis.com/auth/forms.body.readonly — Read-only access to form structure and settings.
      • https://www.googleapis.com/auth/forms.responses.readonly — Read-only access to form responses.
      • https://www.googleapis.com/auth/drive — Full access to Google Drive (required to access forms stored in Drive).
      • https://www.googleapis.com/auth/drive.readonly — Read-only access to Google Drive files.

      For most read-only data ingestion use cases in Nexla, adding https://www.googleapis.com/auth/forms.responses.readonly and https://www.googleapis.com/auth/forms.body.readonly is sufficient.

    5. Click Update, then click Save and Continue to proceed.

    6. If your app is in testing mode, add the Google accounts that should be allowed to authorize the app under Test users. Click Save and Continue.

    7. Review the summary on the final step and click Back to Dashboard.

  5. Create OAuth 2.0 Credentials: Navigate to APIs & Services > Credentials in the left navigation menu. Click Create Credentials, then select OAuth client ID.

    1. Select Web application as the application type.

    2. Enter a descriptive name for the OAuth client (e.g., "Nexla Forms OAuth Client").

    3. Under Authorized redirect URIs, add the Nexla redirect URI. This URI is provided by Nexla and is used to receive the authorization code after the user grants consent.

    4. Click Create to generate the credentials.

    5. Copy both the Client ID and Client Secret displayed in the confirmation dialog.

    Important

    Copy the Client ID and Client Secret immediately when they are displayed. The Client Secret cannot be retrieved again after you close the dialog. Store these credentials securely and never share them publicly or commit them to version control systems.

For complete information about Google OAuth 2.0 setup, see the Google OAuth 2.0 Documentation and the Google Forms API Overview.

Required Information Summary​

Before proceeding to create a credential in Nexla, confirm that you have the following:

  • A Google Cloud project with the Google Forms API enabled.
  • An OAuth 2.0 Client ID from your Google Cloud project credentials.
  • An OAuth 2.0 Client Secret from your Google Cloud project credentials.
  • An OAuth consent screen configured with the appropriate scopes for your use case.

Create a Google Forms API Credential​

  • To create a new Google Forms API credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

Credential Name & Description​

  1. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

    Resource descriptions are recommended but are not required. They should be used to provide information about the resource purpose, data freshness, etc. that can help the owner and other users efficiently understand and utilize the resource.

OAuth 2.0 Authentication Configuration​

The Google Forms API uses OAuth 2.0 authorization code flow. Nexla handles the OAuth redirect and token exchange automatically once you provide your client credentials.

  1. Enter your OAuth 2.0 Client ID in the Client ID field. This is the client identifier obtained from the Google Cloud Console Credentials page when you created the OAuth 2.0 client.

  2. Enter your OAuth 2.0 Client Secret in the Client Secret field. This is the secret value obtained from the Google Cloud Console Credentials page when you created the OAuth 2.0 client.

    The Client ID and Client Secret are sensitive credentials that authenticate Nexla with Google's OAuth 2.0 server. Keep these values secure and do not share them with unauthorized users.

  3. Complete OAuth Authorization: Click Save to initiate the OAuth 2.0 authorization flow. Nexla will redirect you to Google's authorization page, where you will need to:

    1. Sign in with the Google account that has access to the Google Forms you want to integrate with Nexla.

    2. Review the permissions requested by Nexla, which correspond to the scopes configured on your OAuth consent screen.

    3. Click Allow to grant Nexla access to your Google Forms data.

    4. You will be redirected back to Nexla, and the credential will be saved with the OAuth access and refresh tokens.

    The OAuth authorization grants Nexla permission to access your Google Forms data according to the scopes you configured. Nexla stores the authorization tokens securely and automatically refreshes them when needed, so you will not need to re-authorize frequently.

Save the Credential​

  1. Once all of the relevant steps in the above sections have been completed, click the Save button at the bottom of the overlay to save the configured credential. If this is your first time creating this credential, you will be redirected to complete the OAuth authorization flow before the credential is saved.

  2. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.