Google Service Account JSON

In this article

Overview

Use this SnapLogic Account type to connect Snaps to Google BigQuery with a Google service account using a JSON credentials file.

Prerequisites

Limitations and Known Issues

None.

Account Settings

 

  • Asterisk ( * ): Indicates a mandatory field.

  • Suggestion icon ( ): Indicates a list that is dynamically populated based on the configuration.

  • Expression icon ( ): Indicates the value is an expression (if enabled) or a static value (if disabled). Learn more about Using Expressions in SnapLogic.

  • Add icon ( ): Indicates that you can add fields in the fieldset.

  • Remove icon ( ): Indicates that you can remove fields from the fieldset.

Field Name

Field Type

Description

Field Name

Field Type

Description

Label*

 

Default Value: None
Example: Google_Service_Account_JSON

String

Specify a unique label for the account.

 

JSON Key*

Default Value: None
Example: case16370-a0979b67767d.json

String

Specify or upload the relative or absolute path of the JSON file in the SLDB that contains the Private key and other client details.

JSON Key (Cloud Storage)

Default Value: None
Example: case-16870-323549-ef218_cloud.json

String

Specify or upload the relative path of the JSON file to use a Service Account JSON key that is different from the JSON Key described above.

Default Standard SQL

Default Value: Deselected

Checkbox

Select this checkbox to default the dialect in the Query field in the Snaps using this account to Standard SQL.

Use the #legacySQL tag in the Query field of the Snap to treat it as a Legacy SQL Query.

Generating the JSON Key

  1. Create a Service Account in the Google Cloud console. 

  2. Assign a predefined BigQuery role. Alternatively, you can create a custom role and grant permissions to the role.
    Note: Insufficient permissions causes the Snap to fail.

  3. Create a JSON Key containing the public/private key pair. This JSON file is downloaded to your machine when you create the service account. You also must upload it to the SLDB.

 


Related Links

Â