How does OCNORA authenticate with Google Cloud Trace?

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 Trace?

2 typed operations, each with a reference page listing its config fields and the shapes it emits.

What if the Google Cloud Trace operation I need is not listed?

Where Google Cloud Trace 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 Trace?

Not yet. Start from a blank workflow, or describe the workflow to Build with AI.

How are Google Cloud Trace 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.

Google Cloud Trace

Google CloudOAuth 2.0Connection test available

Sends application trace data to Cloud Trace for viewing (Google OAuth2).

OCNORA ships 2 typed Google Cloud Trace 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.

Ask about Google Cloud Trace Google Cloud Trace API docs ↗

Before you connect Google Cloud Trace

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 Trace

Operations, grouped by what they do to your data.

Create and send 1

Create Span

Other operations 1

Batch Write

A sample Google Cloud Trace workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Cloud Trace trigger is needed.
2
Batch Writecloud_trace.batch_write
Batch writes new spans to new or existing traces. You cannot update existing spans. If a span ID already exists, an additional copy of the span will be stored.

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 2