Connections

The workspace connection catalog currently exposes Google Analytics 4 and Google Search Console.

​

Credential custody

The credential service rejects attempts to save OpenRouter as a workspace connector. Exa, AgentMail, and PageSpeed do not have user connection cards.

​

GA4 setup

The numeric property ID is not the browser measurement ID that starts with G-.

​

Search Console setup

Invite the workspace address with Full access, then save gsc_property in brands/<workspace>.yaml as one of:

• A URL-prefix property, such as https://www.example.com/
• A domain property, such as sc-domain:example.com

Domain properties require DNS verification. URL-prefix properties can use the HTML verification token described in Customer-site measurement.

​

Exa setup

Exa is an operator integration, not a workspace connection card. Set EXA_API_KEY in the root environment or repository-root .env. The web worker copies it into the allowlisted measurement or research process only when that job starts. Use the exa measurement preset to exercise both configured modes: There is no Exa Test connection action. A completed Exa run proves that the worker could call the provider. If it fails, inspect the run detail for missing operator configuration, provider rejection, or a retryable transport error.

​

Test flows

The current GA4 and Search Console test is a configuration check. It reads root environment-key presence and the selected workspace property. It does not send a request to Google. The result schema supports four outcomes: The application cannot inspect the Google property member list, so a successful configuration test does not prove that an invitation was completed. Confirm access through the first GA4 or Search Console data pull.

​

Internal integrations

Authority, Gmail, and retrieval services can appear in internal worker paths. They are not part of the current workspace connection catalog. Do not promise a workspace setup flow for them.