Gmail Hook Routing - Architecture Question
@Krill π¦
Goal:
- gpt-5-mini-high agent processes inbound Gmail notifications
- If email is relevant (per filter criteria), agent notifies appropriate user via their connected channel(s)
- Must scale for multiple users, each with multiple channels (Telegram, WhatsApp, iOS)
- Dynamic routing - not hardcoded per-user
Current Architecture:
Gmail Account β Google Pub/Sub β gog (gmail watcher) β Hook endpoint β Agent
- gog: External process watching Gmail via Pub/Sub, posts to /hooks/gmail
- Hook config: Single mapping in hooks.mappings[]
- Agent count: 1 agent spawned per hook invocation (ephemeral)
- Model: github-copilot/gpt-5-mini with thinking: "high"
- Delivery: deliver: false (agent must explicitly send via tool)
- Channel: telegram (single channel specified)
Hook Mapping:
{
match: { path: gmail },
action: agent,
deliver: false,
channel: telegram,
model: github-copilot/gpt-5-mini,
thinking: high,
messageTemplate: <prompt with hardcoded user + channel>
}
Heartbeat Setup (related - caused pollution issue):
{
every: 30m,
target: last,
session: heartbeat // added to isolate from hook context
}
Issues:
1. User/channel routing hardcoded in messageTemplate prompt
2. Single channel value - no multi-channel fanout
3. No userβchannel binding mechanism apparent
4. Unclear what tool agent should use to send notifications
Questions:
1. What tool does the hook-spawned agent use to notify users? (sessions_send? telegram_send? other?)
2. With deliver: false, what does channel: "telegram" do? Context for tool calls?
3. Can clawdbot fanout to multiple channels (Telegram + WhatsApp + iOS) per notification?
4. Idiomatic pattern for multi-user routing where each user has different connected channels?
Goal:
- gpt-5-mini-high agent processes inbound Gmail notifications
- If email is relevant (per filter criteria), agent notifies appropriate user via their connected channel(s)
- Must scale for multiple users, each with multiple channels (Telegram, WhatsApp, iOS)
- Dynamic routing - not hardcoded per-user
Current Architecture:
Gmail Account β Google Pub/Sub β gog (gmail watcher) β Hook endpoint β Agent
- gog: External process watching Gmail via Pub/Sub, posts to /hooks/gmail
- Hook config: Single mapping in hooks.mappings[]
- Agent count: 1 agent spawned per hook invocation (ephemeral)
- Model: github-copilot/gpt-5-mini with thinking: "high"
- Delivery: deliver: false (agent must explicitly send via tool)
- Channel: telegram (single channel specified)
Hook Mapping:
{
match: { path: gmail },
action: agent,
deliver: false,
channel: telegram,
model: github-copilot/gpt-5-mini,
thinking: high,
messageTemplate: <prompt with hardcoded user + channel>
}
Heartbeat Setup (related - caused pollution issue):
{
every: 30m,
target: last,
session: heartbeat // added to isolate from hook context
}
Issues:
1. User/channel routing hardcoded in messageTemplate prompt
2. Single channel value - no multi-channel fanout
3. No userβchannel binding mechanism apparent
4. Unclear what tool agent should use to send notifications
Questions:
1. What tool does the hook-spawned agent use to notify users? (sessions_send? telegram_send? other?)
2. With deliver: false, what does channel: "telegram" do? Context for tool calls?
3. Can clawdbot fanout to multiple channels (Telegram + WhatsApp + iOS) per notification?
4. Idiomatic pattern for multi-user routing where each user has different connected channels?
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
130,529Members
Resources
Similar Threads
Was this page helpful?
