Skip to main content
You need permission to create service accounts, grant roles and create keys in the Google Cloud project, such as the Service Account Admin, Service Account Key Admin and Project IAM Admin roles.

Creating a service account key

Work in the Google Cloud project you are connecting. The roles you grant the service account decide which actions work.

1

Enable the required APIs

Sign in to the Google Cloud Console and select the project. Turn on the Identity and Access Management (IAM) API, Secret Manager API and Cloud Resource Manager API.

  • For each API, search for it in Search (/) for resources, docs, products, and more and open it.
  • Click Enable.
  • If the page shows Manage and API Enabled, the API is already on.
2

Create the service account

Open IAM & Admin > Service Accounts.

  • Click Create service account.
  • Service account name: StackOne Integration
  • Click Create and continue.
Create service account form with the Service account name field and the Create and continue button highlighted.
3

Grant the roles

Under Permissions (optional), add a role for each kind of action you plan to use.

  • Click Select a role.
  • Search for Reader.
  • Select Reader for read-only access to service accounts, keys, roles, secrets, IAM policies, projects and tags. It doesn’t include secret values.
  • For each kind of resource you create, change or delete, click Add another role and add its role.
  • Secret Manager Admin: secrets and secret versions, including secret values and secret IAM policies
  • Service Account Admin: service accounts
  • Service Account Key Admin: service account keys
  • Role Administrator: custom roles
  • Project IAM Admin: the project IAM policy
  • Project Mover: the project’s display name
  • Tag Administrator: tag keys and tag values
  • To read secret values without managing secrets, add Secret Manager Secret Accessor instead of Secret Manager Admin.
  • Organization details, creating projects and the folder actions need roles on the organization, such as Organization Viewer, Folder Viewer and Project Creator. Only an organization administrator can grant them, on the organization’s IAM page rather than the project’s.
  • Click Continue.
  • Click Done.
  • New roles can take a few minutes to become active.
Permissions step of the Create service account form with the Reader role and the Continue button highlighted.
4

Create the JSON key

In Service Accounts, click the email of the new service account and open the Keys tab.

  • Click Add key.
  • Select Create new key.
  • Key type: JSON
  • Click Create. The key file downloads once, and Google can’t recover it if it is lost.
  • If your organization blocks key creation with an organization policy, ask an organization policy administrator to allow it for this project.
Create private key dialog with the JSON key type and the Create button highlighted.

Entering the key

Open the downloaded .json key file in a text editor. The whole file, including the outer braces, is the key.

  • Copy the Service Account Key (JSON) across.
  • Copy the project_id value across to GCP Project ID, or use the ID of another project the service account has roles on.
1

Connect

  • Click Connect.
  • If applicable, the provider will redirect you to a sign-in or authorization page. Complete the provider’s authorization flow.
  • Once authorization is successful, you will see a confirmation popup.
2

Use Actions

Connect an AI platform to the linked account’s actions. See AI Platforms.Other ways to call actions are listed in Protocols & SDKs.