Supported Features
Account Deletion Account ProvisioningIntegration Overview
There are two integration methods for Google Cloud Platform: OAuth and API Key. Review the features below and choose the method that best fits your management needs.| Available Actions / Integration Method | OAuth (New) | API (Old) |
|---|---|---|
| Integration unit | All projects in bulk | Per project |
| Administrator | Account administrator | Project administrator |
| Supported actions | User sync, deletion | User sync only |
OAuth Integration (New: Recommended)
Prerequisites
Logging In to Google Cloud Platform
Go to the Google Cloud Platform login page and enter the email address and password of an administrator account.Enabling the Cloud Resource Manager API
- After logging in to Google Cloud Platform, create a project or navigate to the project you want to integrate.
- Go to APIs & Services > Enabled APIs & Services and click Enable APIs and Services.

- Search for Cloud Resource Manager API and click Enable.

Creating an OAuth Application for Integration
- After logging in to Google Cloud Platform, go to APIs & Services > OAuth consent screen.
- Select
Internalfor the User Type and click Create. If you see “Error 403: org_internal” and the integration fails, create with User TypeExternal.

- Enter the application name (e.g., Admina), user support email, and developer contact email in the app information, then click Save and Continue.
- Click Add or Remove Scopes and add one of the following Scope URLs. The image shows an example scope configuration for Read & Write.
- Read & Write (to allow user sync and deletion):
https://www.googleapis.com/auth/cloud-platform - Read Only (to allow user sync only):
https://www.googleapis.com/auth/cloud-platform.read-only

- Click the Credentials menu, then click + Create Credentials > OAuth client ID.

- Fill in the OAuth client ID creation form as follows and click Create.
- Application type:
Web application - Name: Any name (e.g., Admina)
- Authorized redirect URIs:
https://itmc.i.moneyforward.com/oauth/callback

- Copy the displayed Client ID and Client Secret values.

Integration Setup
- In the MoneyForward Admina integrations screen, search for Google Cloud Platform. Select the OAuth tab.
- Enter the Client ID and Client Secret, then click Connect. For Permissions, select the option that matches the scope configured in step 7.

API Key Integration (Old)
Prerequisites
Logging In to Google Cloud Platform
Go to the Google Cloud Platform login page and enter the email address and password of an administrator account.Enabling the Cloud Resource Manager API
- After logging in to Google Cloud Platform, navigate to the project you want to integrate.
Integration is performed on a per-project basis. Select the project whose users you want to retrieve, then complete the integration. You can integrate multiple projects by repeating this process.
- Go to APIs & Services > Enabled APIs & Services and click Enable APIs and Services.

- Search for Cloud Resource Manager API and click Enable.

Creating a Service Account for Integration
- Go to APIs & Services > Credentials, click [CREATE CREDENTIALS], and select [Service account].

- Enter any name in the Service Account Name field and click [CREATE AND CONTINUE].

- Configure the role. Select Security Reviewer and click Continue. Finally, click Done.

Creating a Private Key
- From Service Accounts, click the service account name you created, then go to the [KEYS] tab > ADD KEY > Create new key.

- Select JSON as the Key type and click CREATE.

- A JSON file will be downloaded — save it. Open it with a text editor to review the contents. All parameters required for the integration are included in this JSON file.
Integration Setup
- In the MoneyForward Admina integrations screen, search for Google Cloud Platform. Switch to the API tab.

- Enter the following values from the downloaded JSON file and click Connect.

- Workspace Key: Enter the
project_id - Service Account Email: Enter the
client_email - Private Key: Enter the
private_key. Enter from -----BEGIN PRIVATE KEY----- to -----END PRIVATE KEY-----. (The leading"and trailing\n",are not needed.)
If an error appears, refer to the following help article.

