Googleapis Chromeuxreport

Google Chrome UX Report API provides real-user web performance experience data collected from Chrome users.

Type: Tool
Category: Cloud
Version: 1.0.0
Provider: InTouch AI
License: MIT

Provided free and as is, without warranty of any kind — including merchantability, fitness for a particular purpose, and the accuracy or completeness of any result. See the licence. You are responsible for checking what this produces before relying on it.

cloudgoogleapisreport

Googleapis Chromeuxreport

Google Chrome UX Report API provides real-user web performance experience data collected from Chrome users.

Base URL: https://chromeuxreport.googleapis.com
Auth: bearer (pass your key via the apiKey input)

Operations

chromeuxreport_records_queryhistoryrecord — POST /v1/records:queryHistoryRecord — Queries the Chrome User Experience Report for a timeseries history record for
chromeuxreport_records_queryrecord — POST /v1/records:queryRecord — Queries the Chrome User Experience for a single record for a given site. Retur

Inputs

apiKey — your googleapis-chromeuxreport API key
operation — one of the operations above
path parameters when an operation's path contains {...}
query — optional JSON object of query params
body — JSON object for create/update ops

Example

operation: chromeuxreport_records_queryhistoryrecord
apiKey: <your key>

Publishes

The keys a later task may reference as {{taskName.key}}. Referencing anything not listed here resolves to nothing at run time.

error
operation
result
status

Input Properties

Every property this tool accepts, from its own tool.iml.

Property	Type	Required	Default	Description
`apiKey`	string	yes	—	DEPRECATED — bind an API Key credential to the task with `credentialName` instead. A key pasted here is stored in the workflow definition in clear and appears in every export of it. Still honoured for workflows built before the change.
`operation`	string	yes	—	One of: chromeuxreport_records_queryhistoryrecord, chromeuxreport_records_queryrecord
`body`	string	no	—	Request body as a JSON object string (for create/update operations).
`query`	string	no	—	Query-string parameters as a JSON object string, e.g. {"limit": 50}. Parsed and url-encoded onto the request.