Sheets
Tabular evidence ingestion, schema inference, filtering, summarization, charts, exports, and handoff.
Validate Sheets in BrowserOps
BrowserOps checks the public page, metadata, accessibility, console state, network failures, trace propagation, and screenshot evidence without taking over Sheets's product role.
- Target
- https://sheets.platphormnews.com
- Journey
- sheets homepage smoke
Boundary
Public preview validates intent. Browserbase runs create real browser evidence. Downstream delivery is tracked as a handoff and is never marked accepted without a response.
Integration run state
Preview the BrowserOps plan publicly, then run a Browserbase-backed check through BrowserOps-managed service credentials.
Live Public Connectivity
Sheets public surfaces are reachable; configure a BrowserOps receive-handoff route before claiming downstream delivery.
health
200passed
trace echo not confirmed
apiDocs
200passed
trace echo not confirmed
llms
200passed
trace echo not confirmed
mcp
200passed
trace echo not confirmed
handoffReceiver
no responsedegraded
trace echo not confirmed
Browserbase Runtime
BrowserOps runs for Sheets use browserbase. Browserbase is configured, project is configured, and session metadata records BrowserOps run ID, journey ID, and target service without storing target URLs in Browserbase metadata.
Capability Mapping
BrowserOps may call
- create_evidence_table
- append_public_run_summary
BrowserOps may receive
- route_matrix_ready
- test_matrix_ready
Transport and Boundary
- Preferred transports
- openapi, csv, mcp
- API docs
- https://sheets.platphormnews.com/api/docs
- MCP status
- not advertised
- Auth boundary
- Public schema reads may be safe; report export and sheet creation use BrowserOps-managed service credentials or service-to-service authorization.
Handoff Examples
Sheets remains the tabular evidence surface; BrowserOps does not claim export until accepted.