Google Access Context Manager
An API for setting attribute based access control to requests to Google Cloud services (Google OAuth2).
OCNORA ships 10 typed Google Access Context Manager 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 Access Context Manager
- 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 Access Context Manager
Operations, grouped by what they do to your data.
Create and send 2
Delete and cancel 2
A sample Google Access Context Manager workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Access Context Manager trigger is needed.
- 2Get Access Levelaccess_context_manager.get_access_levelGets an access level based on the resource name.
- 3Create Access Levelaccess_context_manager.create_access_levelCreates an access level.
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 10
- Create Access LevelCreates an access level.access_context_manager.create_access_level
- Create Access PolicyCreates an access policy.access_context_manager.create_access_policy
- Delete Access LevelDeletes an access level based on the resource name.access_context_manager.delete_access_level
- Delete Access PolicyDeletes an access policy based on the resource name.access_context_manager.delete_access_policy
- Get Access LevelGets an access level based on the resource name.access_context_manager.get_access_level
- Get Access PolicyReturns an access policy based on the name.access_context_manager.get_access_policy
- List Access LevelsLists all access levels for an access policy.access_context_manager.list_access_levels
- List Access PoliciesLists all access policies in an organization.access_context_manager.list_access_policies
- Update Access LevelUpdates an access level.access_context_manager.update_access_level
- Update Access PolicyUpdates an access policy.access_context_manager.update_access_policy
Google Access Context Manager questions
- How does OCNORA authenticate with Google Access Context Manager?
- 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 Access Context Manager?
- 10 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google Access Context Manager operation I need is not listed?
- Where Google Access Context Manager 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 Access Context Manager?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google Access Context Manager 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 Access Context Manager 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.