Google

Google services share OAuth app setup, while each API has its own scopes and access requirements. Typenode supports managed access for Google Search Console; the current Google Analytics reporting Template requires a custom app. Use the service references below for the exact requirements.

Each service reference lists its API identifiers, exact OAuth scopes and resource-access conditions. Read it together with the shared Google setup below.

Google sign-in to Typenode is separate from giving a Workflow access to Google data. See Managed and custom OAuth apps for registration ownership, account consent and how that access becomes a Workflow Secret.

For the managed route, Typenode maintains the Google Cloud project and enables its supported APIs. You do not need to create your own Cloud project to use that route. Your Google account must already have access to the resources the task concerns; consent does not grant product or resource access. Each service reference explains its specific access requirements.

A custom Google app uses a Google Cloud project your organisation maintains. Follow Google Cloud OAuth setup for the registration steps. The service reference lists the APIs to enable in that project and the exact scopes the task needs.

You can reuse an existing registration across Google services when its project and allowed scopes cover their requirements. Sharing a registration does not make every Google API available through it, and changing the registration owner does not give the connected account access to other organisations' data.

Start with the operation's required API and exact OAuth scopes. Compare them with the enabled managed APIs and scope lists in the service references, then check the account's access and any additional Google product eligibility requirements. Request only that task's scopes, or the individual Template Credential's declared list.

Check the service reference and Google's documentation for the operation. A scope appearing on a consent screen does not establish that the required API is available or that the account can use it. If a Google service has no reference here, ask your Agent to establish its requirements before choosing an app.

If the task requires an API not enabled for the managed route, or scopes outside its allowlist, use a suitable custom app or ask Typenode about managed availability. Enabling an API in your own project does not change Typenode's managed project.

If the API and scopes fit but a request is refused, check the actual grant, account, property, method and service requirements. Missing resource access is not automatically a reason to switch to a custom app. A problem with Typenode's managed registration needs Typenode to repair it.