How does OCNORA authenticate with Google Chrome UX Report?

With a stored API key credential, shaped the API key as raw text. A connection test can check it when you add it.

What can I automate with Google Chrome UX Report?

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

What if the Google Chrome UX Report operation I need is not listed?

Where Google Chrome UX Report 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 Chrome UX Report?

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

How are Google Chrome UX Report 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 Chrome UX Report

Google CloudAPI keyConnection test available

The Chrome UX Report API lets you view real user experience data for millions of websites (Google API key).

OCNORA ships 2 typed Google Chrome UX Report 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 Chrome UX Report Google Chrome UX Report API docs ↗

Before you connect Google Chrome UX Report

Authentication: API key
Credential: the API key as raw text
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 Chrome UX Report

Operations, grouped by what they do to your data.

Read and search 2

A sample Google Chrome UX Report workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Chrome UX Report trigger is needed.
2
Query History Recordchrome_ux_report.query_history_record
Queries the Chrome User Experience Report for a timeseries history record for a given site.

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