Google IAM Service Account Credentials
Creates short-lived credentials for impersonating IAM service accounts (Google OAuth2).
OCNORA ships 4 typed Google IAM Service Account Credentials operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.
Before you connect Google IAM Service Account Credentials
- Authentication
- OAuth 2.0
- Credential
- {"client_id", "client_secret", "refresh_token"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
What you can do with Google IAM Service Account Credentials
Operations, grouped by what they do to your data.
Create and send 2
Read and search 2
A sample Google IAM Service Account Credentials workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google IAM Service Account Credentials trigger is needed.
- 2Get Allowed Locationsiam_credentials.get_allowed_locationsReturns the trust boundary info for a given service account.
- 3Generate Access Tokeniam_credentials.generate_access_tokenGenerates an OAuth 2.0 access token for a service account.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 4
- Generate Access TokenGenerates an OAuth 2.0 access token for a service account.iam_credentials.generate_access_token
- Generate Id TokenGenerates an OpenID Connect ID token for a service account.iam_credentials.generate_id_token
- Get Allowed LocationsReturns the trust boundary info for a given service account.iam_credentials.get_allowed_locations
- Get Allowed Locations Workforce PoolReturns the trust boundary info for a given workforce pool.iam_credentials.get_allowed_locations_workforce_pool
Google IAM Service Account Credentials questions
- How does OCNORA authenticate with Google IAM Service Account Credentials?
- With a stored OAuth 2.0 credential, shaped {"client_id", "client_secret", "refresh_token"}. A connection test can check it when you add it.
- What can I automate with Google IAM Service Account Credentials?
- 4 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google IAM Service Account Credentials operation I need is not listed?
- Where Google IAM Service Account Credentials has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Google IAM Service Account Credentials?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google IAM Service Account Credentials calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
See your first Google IAM Service Account Credentials workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.