Google BigQuery Data Policy
Allows users to manage BigQuery data policies (Google OAuth2).
OCNORA ships 6 typed Google BigQuery Data Policy 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 BigQuery Data Policy
- 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 BigQuery Data Policy
Operations, grouped by what they do to your data.
Create and send 2
Read and search 2
Update 1
Delete and cancel 1
A sample Google BigQuery Data Policy workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google BigQuery Data Policy trigger is needed.
- 2Get Data Policybigquery_data_policy.get_data_policyGets the data policy specified by its resource name.
- 3Add Granteesbigquery_data_policy.add_granteesAdds new grantees to a data policy. The new grantees will be added to the existing grantees. If the request contains a duplicate grantee, the grantee will be ignored.
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 6
- Add GranteesAdds new grantees to a data policy. The new grantees will be added to the existing grantees. If the request contains a duplicate grantee, the grantee will be ignored.bigquery_data_policy.add_grantees
- Create Data PolicyCreates a new data policy under a project with the given `data_policy_id` (used as the display name), and data policy type.bigquery_data_policy.create_data_policy
- Delete Data PolicyDeletes the data policy specified by its resource name.bigquery_data_policy.delete_data_policy
- Get Data PolicyGets the data policy specified by its resource name.bigquery_data_policy.get_data_policy
- List Data PoliciesList all of the data policies in the specified parent project.bigquery_data_policy.list_data_policies
- Update Data PolicyUpdates the metadata for an existing data policy.bigquery_data_policy.update_data_policy
Google BigQuery Data Policy questions
- How does OCNORA authenticate with Google BigQuery Data Policy?
- 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 BigQuery Data Policy?
- 6 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google BigQuery Data Policy operation I need is not listed?
- Where Google BigQuery Data Policy 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 BigQuery Data Policy?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google BigQuery Data Policy 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 BigQuery Data Policy 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.