Create Sink
cloud_logging.create_sink
ActionGoogle Cloudconnection required
Calls POST /projects/{project}/sinks?uniqueWriterIdentity=true.
Create a log export sink to BigQuery, Cloud Storage, Pub/Sub or a log bucket.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google Cloud Logging
- Secret shape
- {"client_id", "client_secret", "refresh_token"}
- Config it needs
- project_id
- Resolved by
- config.connection_id, else node.connection_id
Configuration
10 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
project_id GCP project id (overrides connection). | string | No | — | — | — |
sink_name Sink id, unique in the project. | string | Yes | — | — | — |
destination Export target, e.g. bigquery.googleapis.com/projects/p/datasets/d. | string | Yes | — | — | — |
filter Logging filter selecting what to export (empty exports everything). | string | No | — | — | — |
description What this sink is for. | string | No | — | — | — |
disabled true to create the sink switched off. Blank or false creates it live. | string | No | — | — | — |
include_children true to also export logs from child resources (folder/org sinks). | string | No | — | — | — |
exclusions Exclusion filters (JSON array of {name, filter, disabled}). | array | No | — | array of object | — |
bigquery_options BigQuery options (JSON), e.g. {"usePartitionedTables": true}. | object | No | — | — | {"usePartitionedTables":true} |
unique_writer_identity Mint a dedicated writer service account (recommended). | boolean | No | true | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"bigquery_options": {
"usePartitionedTables": true
},
"unique_writer_identity": true
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok | boolean | — |
name Sink id. | string | — |
destination Where the sink exports to. | string | — |
filter Logging filter the sink exports. | string | — |
disabled True while the sink is switched off. | boolean | — |
description The sink's human description. | string | — |
writer_identity Service account the destination must grant write access to. | string | — |
include_children True when the sink also exports children of the parent resource. | boolean | — |
intercept_children True when child resources' logs are intercepted here. | boolean | — |
exclusions Exclusion filters attached to the sink; each one suppresses matching logs. | array | — |
bigquery_options BigQuery destination options (partitioned tables). | object | — |
create_time When the sink was created. | string | — |
update_time When the sink was last changed. | string | — |
resource_name Full resource name of the sink, when the API returns one. | string | — |
{
"bigquery_options": {},
"create_time": "",
"description": "",
"destination": "",
"disabled": false,
"exclusions": [],
"filter": "",
"include_children": false,
"intercept_children": false,
"name": "",
"ok": false,
"resource_name": "",
"update_time": "",
"writer_identity": ""
}Related Google Cloud Logging nodes
Solutions with Google Cloud Logging
See Create Sink run in a workflow.
In a technical demo we add the Google Cloud Logging connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.