Add Grantees

bigquery_data_policy.add_grantees
ActionGoogle Cloudconnection required

Calls BigQuery Data Policy POST /v2/projects/{projectsId}/locations/{locationsId}/dataPolicies/{dataPoliciesId}:addGrantees.

Adds 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.

Connection

Required
Yes — the node will not save without one
Auth type
OAuth 2.0
Providers
Google BigQuery Data Policy
Secret shape
{"client_id", "client_secret", "refresh_token"}
Config it needs
location, project_id
Resolved by
config.connection_id, else node.connection_id

Configuration

4 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
project_id
GCP project id (overrides connection).
stringNo———
location
Location / region (overrides connection).
stringNo———
data_policy
Data policy id.
stringYes———
body
Request body (AddGranteesRequest) as JSON.
objectNo———

Output

One shape.

result

FieldTypeExample
ok
boolean—
dataGovernanceTag
object—
dataPolicyId
string—
etag
string—
grantees
array—
version
string—
dataMaskingPolicy
object—
{
  "dataGovernanceTag": {},
  "dataMaskingPolicy": {},
  "dataPolicyId": "",
  "etag": "",
  "grantees": [],
  "ok": false,
  "version": ""
}

See Add Grantees run in a workflow.

In a technical demo we add the Google BigQuery Data Policy connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.