Google Cloud Logging
Write and query log entries in Google Cloud Logging (Google OAuth2).
OCNORA ships 10 typed Google Cloud Logging 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 Cloud Logging
- 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 Cloud Logging
Operations, grouped by what they do to your data.
Create and send 1
Read and search 4
Update 2
Delete and cancel 2
Other operations 1
A sample Google Cloud Logging workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Cloud Logging trigger is needed.
- 2Get Sinkcloud_logging.get_sinkRead one log export sink, including the writer identity to grant.
- 3Create Sinkcloud_logging.create_sinkCreate a log export sink to BigQuery, Cloud Storage, Pub/Sub or a log bucket.
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 SinkCreate a log export sink to BigQuery, Cloud Storage, Pub/Sub or a log bucket.cloud_logging.create_sink
- Delete LogDeletes all the log entries in a log for the global _Default Log Bucket.cloud_logging.delete_log
- Delete SinkDelete a log export sink from a project.cloud_logging.delete_sink
- Get SinkRead one log export sink, including the writer identity to grant.cloud_logging.get_sink
- List EntriesQuery Cloud Logging entries in a project with a filter.cloud_logging.list_entries
- List LogsList the log ids that have entries in a project.cloud_logging.list_logs
- List SinksList Cloud Logging export sinks in a project.cloud_logging.list_sinks
- Update SinkPatch a log export sink — destination, filter, exclusions or disabled state.cloud_logging.update_sink
- Update Sink ProjectsUpdates a sink.cloud_logging.update_sink_projects
- Write LogWrite one entry to a Cloud Logging log (text or JSON payload).cloud_logging.write_log
Where Google Cloud Logging fits
Google Cloud Logging questions
- How does OCNORA authenticate with Google Cloud Logging?
- 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 Cloud Logging?
- 10 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google Cloud Logging operation I need is not listed?
- Where Google Cloud Logging 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 Cloud Logging?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google Cloud Logging 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 Cloud Logging 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.