Triage The Inbox
Classify inbox items and propose priorities; never changes mailbox state.
Caller- chat
Agent- triage-the-inbox-analyst
Gateway- triage-the-inbox-readonly
Pooltriage-the-inbox-pool
- triage-the-inbox-model
Toolsgmail
Toolsgoogle-calendar
What this template gives you
Interface
A chat window, in your browser
Use the included interface to send a request to this template.
Gateway
triage-the-inbox-readonly gateway
This template sends its requests through triage-the-inbox-readonly gateway, where its access rules and limits apply.
Model
triage-the-inbox-model
This template uses triage-the-inbox-model through the triage-the-inbox-pool pool.
Usage
Hand this template to an AI agent to set up this template
Node.js and npm to run npx.
Dome CLI, installed with brew install dome-systems/tap/dome, then signed in with dome auth login.
Docker Compose to run the companion app locally.
- 1
Create a workspace
dome workspaces create --name <workspace-name>The CLI creates and selects a workspace context for you.
- 2
Confirm the workspace context
dome context listThe workspace you just created is already selected.
- 3
Pull the template
npx @domesystems/templates pull dome-systems/triage-the-inbox@0.1.1 --dir triage-the-inboxDownloads this immutable release and verifies its digest.
- 4
Run the template
npx @domesystems/templates up --dir triage-the-inboxImports it into Dome and starts the companion app.
Dome import variables
npx @domesystems/templates up imports the template into Dome and prompts for required values. For unattended runs, set them as DOME_IMPORT_VAR_… environment variables.
Required values
DOME_IMPORT_VAR_google_oauth_client_idDOME_IMPORT_VAR_google_oauth_client_secretDOME_IMPORT_VAR_anthropic_api_key
Setup guide
Follow this template's setup guidance for agent variables and upstream connections.
# Set up Triage The Inbox
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
- `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
### 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 Calendar
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 Calendar API** and **Google Calendar 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 Calendar and Calendar MCP APIs, register the redirect URI shown by Dome, and retain only the calendar list, free/busy, and event read scopes.
## 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.Runtime environment
These variables are required to run the agent. During pull, .env.example is copied to .env when available. If they’re missing, npx @domesystems/templates up retrieves them from Dome and saves them in .env. Pass --provision to refresh them.
DOME_TOKEN=
DOME_GATEWAY_URL=Agent instructions
You are Triage The Inbox, a read-only assistant. Classify inbox items and propose priorities; never changes mailbox state.
Use connected tools only to retrieve information. Do not invoke tools that create, update, delete, send, approve, or change upstream state, even if a provider exposes them. Produce a clear answer with source-specific evidence, confidence, assumptions, and recommended human next steps. When an action is needed, draft or recommend it for a person to perform; do not perform it.