1. Set up a Google BigQuery connection
Start establishing a connection to Google BigQuery in either of the following ways:
- From the Resources menu, select Connections. Then, click + Create connection at the top right.
– or –
- While working in a new or existing integration, you can add an application to a flow simply by clicking Add source or Add destination.
In the resulting Application list, click Google BigQuery.
The Create connection pane then asks you to name the new connection.
Be sure to provide a clear and distinguishable Name as soon as the connection is created. Throughout integrator.io imports and exports, you will have the option to choose this new connection, and a unique identifier will prove helpful later when selecting among a list of connections that you’ve created.
Click Next to configure the connection.
2. Supply required Google BigQuery account information
At this point, you’re presented with settings for Google BigQuery authentication.
Configure scopes (required): Scopes are permissions that the Google BigQuery API defines to limit the access to your account. To select the scopes for this connection,
- Click the Configure scopes button.
- To access all of the scopes in the API, click the
– or –
Check the scopes you want to add, and click the button.
- Click Save when you’re ready to leave the editor and finish setting up your connection.
Configure your client id and secret (required): Check this box to reveal iClient options.
iClient (required): Select the iClient pair that stores the client ID and client secret provided to you by Google BigQuery. To add an iClient and configure your credentials, click the plus (+) button. Click the edit ( ) button to modify a selected iClient. Be sure to give the iClient a recognizable name for use in any other connections.
Callback URL (read-only): Copy this integrator.io callback URL to provide directions to Google BigQuery for where to go after authentication. (This URL should be whitelisted with the authorization server.)
Sign in to your Google BigQuery account at console.cloud.google.com/bigquery, and select Credentials from the APIs & services menu.
On your first visit, Google BigQuery encourages you to customize the consent screen with, among other things, the scopes (API permissions) for third-party apps. Click Configure consent screen.
Select whether the application will be Public or Internal, and then proceed to the OAuth consent screen page. At minimum, provide an application name, review the scopes and add or remove scopes if necessary, and enter integrator.io into the list of Authorized domains.
Click Save and return to the Credentials page. To create an OAuth client ID, click + Create credentials > OAuth client ID at the top.
Google Cloud Platform next asks you which type of OAuth client ID you’re creating. Select Web application page, and at minimum give it a unique name and paste the Callback URL above into the application’s Authorized redirect URIs. Click Create.
BigQuery confirms the new OAuth client ID’s creation and shares its client ID and client secret for the iClient values in the connection.
3. Edit advanced Google BigQuery settings
Before continuing, you have the opportunity to provide additional configuration information, if needed, for the Google BigQuery connection.
4. Save and authorize
Once you have configured the Google BigQuery connection, you have a couple options for continuing:
- Save & authorize – click this button to test the connection, commit the new connection so that it will be available to all integrations for your account (and applied to the current source or destination app, if you created it within a flow)
- Cancel – click to exit without saving any new changes
When you select Save & authorize, you are presented with a Google BigQuery form in a new browser window.
After signing in, review the permissions for the integration and click Allow.
The browser window closes, and the new connection is now successfully added to your account. It will be applied to the current source or destination app, if you created it within a flow. Otherwise, you may proceed to register the connection with an integration.