# Set up Read Out Experiments

This is a read-only composite, but it needs a model credential and every listed data source configured before it can run. Set up isolated test accounts or workspaces first, grant only the smallest read scope that exposes the test data, and store every credential only in Dome's secret inputs. Never put a key or secret in this repository, an agent prompt, or a chat message.

## Create the model credential

- Create an API key in the [Anthropic Console](https://console.anthropic.com/settings/keys).
- Enter the raw key as `anthropic_api_key` during import. Do not prepend `Bearer `.
- The template uses that key only for its managed `claude-sonnet-5` model connection.

## Create the provider credentials

- `intercom_bearer_token`: An Intercom workspace access token
- `google_oauth_client_id`: A Google OAuth client ID for an AI-powered agent.
- `google_oauth_client_secret`: The Google OAuth client secret.

For a provider that asks you to register a manual OAuth app, use this callback URL exactly:

`https://api.domesystems.ai/oauth/callback`

## Set up each connected provider

### Amplitude

This provider uses Dynamic Client Registration (DCR). Do **not** create or paste an OAuth client ID or client secret: after import, Dome registers the client and opens the provider's consent page.

After saving, authorize a test Amplitude user that can view only the required projects. This composite uses the US endpoint and read-only OAuth; confirm project access with `get_amplitude_context`.

### PostHog

This provider uses Dynamic Client Registration (DCR). Do **not** create or paste an OAuth client ID or client secret: after import, Dome registers the client and opens the provider's consent page.

PostHog's hosted MCP server supports OAuth. This composite uses the upstream
`readonly=true` option, which removes write MCP tools from the session.

- After import, complete shared OAuth as a dedicated test member and select the
  intended organization and project. Verify a known test insight or event is
  visible and another project is unavailable.

PostHog's MCP exposes a generic `exec` tool, so tool-name filtering alone is
not a complete read-only boundary. Keep the upstream read-only setting, and pin
the connection to one project when production use requires a fixed boundary.
For a headless connection, use a separate personal API key with PostHog's MCP
Server preset instead of modifying this OAuth template.

### Intercom

- `intercom_bearer_token`: enter `Bearer ` followed by an Intercom workspace access token. Use a token with only the approved read permissions for the workspace this agent will inspect.

This composite uses bearer-token authentication, not OAuth. It does not open a browser, require a callback URL, or require Intercom to allowlist Dome's OAuth callback.

Create or find the workspace token in **Intercom Developer Hub → Your Apps**. Open the private app that matches the workspace name—migrated workspaces may label it **Access Token App**—then open **Authentication** to reveal the access token and review its scopes. Intercom's [workspace access-token walkthrough](https://community.intercom.com/getting-started-with-intercom-43/api-how-to-set-up-an-access-bearer-token-a-k-a-find-workspace-access-token-7212) shows these steps; its [MCP guide](https://developers.intercom.com/docs/guides/mcp) documents the bearer-token header and permissions.

Store the raw token only in Dome's secret input, prefixed with `Bearer `. Do not put it in this repository, an agent instruction, or a prompt. Use `https://mcp.eu.intercom.com/mcp` instead of the configured US endpoint only for an EU-hosted Intercom workspace.

### Gmail

Before import, open [Google Cloud OAuth clients](https://console.cloud.google.com/auth/clients/create) and create a **Web application** OAuth client. Enable **Use this client for an AI-powered agent**, add `https://api.domesystems.ai/oauth/callback` as an authorized redirect URI, and copy the client ID and secret. In **APIs & Services → Library**, enable both **Gmail API** and **Gmail MCP API** for that same project. Configure the consent screen as **Internal**, or add the test user if it is **External**.

- `google_oauth_client_id` and `google_oauth_client_secret`: enter values from a Google Cloud Web OAuth client configured as an AI-powered agent.

Enable the Gmail and Gmail MCP APIs, add only `gmail.readonly`, and register the redirect URI shown by Dome. Use a test mailbox for the first connection.

### Google Drive

Before import, open [Google Cloud OAuth clients](https://console.cloud.google.com/auth/clients/create) and create a **Web application** OAuth client. Enable **Use this client for an AI-powered agent**, add `https://api.domesystems.ai/oauth/callback` as an authorized redirect URI, and copy the client ID and secret. In **APIs & Services → Library**, enable both **Google Drive API** and **Google Drive MCP API** for that same project. Configure the consent screen as **Internal**, or add the test user if it is **External**.

- `google_oauth_client_id` and `google_oauth_client_secret`: enter values from a Google Cloud Web OAuth client configured as an AI-powered agent.

Enable the Drive and Drive MCP APIs, register the redirect URI shown by Dome, and request only `https://www.googleapis.com/auth/drive.readonly`.

### Notion

This provider uses Dynamic Client Registration (DCR). Do **not** create or paste an OAuth client ID or client secret: after import, Dome registers the client and opens the provider's consent page.

Importing the template creates the Notion connection and
attaches it to the gateway without waiting for a tool catalog. In the
connection step, sign in to Notion with an account that can access the
workspace or pages the agent should search, then approve the requested
connection. After authorization, refresh the Notion connection's tools so the
gateway can use the discovered catalog. Dome uses the API key only to create
the shared model connection; Sandbox does not retain the value.

## Import and verify

1. Import the template and provide the values above.
2. Complete every browser OAuth flow with the intended dedicated test user. Token-based sources do not open a browser.
3. Open **Tools**, refresh discovery, and confirm every connection is attached to the template gateway.
4. Run the managed agent against known test data. Treat the template as verified only when the run succeeds **and calls at least one expected read-only tool**.

If a connection is unreachable, check the provider section above for its callback, API/MCP enablement, token prefix, consent scopes, and user/workspace access before retrying.