Inbox & event sources

Inbox

The Inbox shows inbound events for your workspace. Use the Events and Sources tabs in the dashboard. Custom Herald URLs live under Sources / Custom URL.

Event sources

Event sources are per-provider inbound hooks with setup guides. Open Inbox → Sources to configure:

• Stripe — payment and subscription events
• GitHub Actions — workflow / CI failures
• Sentry — issue alerts for triage
• Custom Herald URL — any JSON POST with optional x-herald-secret
• Web3 — Alchemy, Tenderly, Forta, Helius (Solana), and related monitors

Each source gets a unique inbound URL. Herald normalizes payloads into a common shape — title, severity, dashboard link, and source-specific fields when available — so agents can triage without parsing raw JSON.

Inbound URL format

POST /api/hooks/{workspaceId}/{hookId}

Authentication depends on the source. Provider hooks may accept provider-specific signatures; Herald webhooks use x-herald-secret. See Herald webhooks for custom inbound endpoints.

MCP inbox tools

After connecting your IDE, agents get read-only inbox tools (when the key allows inbox tools):

list_recent_events

List recent inbound events (default 10, max 50). Use before formatting structured alerts.

get_event

Fetch a single event by ID from list_recent_events, including normalized fields and raw payload.

Typical agent workflow

1. Event source receives an ops or monitoring event
2. Agent calls list_recent_events to see new payloads
3. Agent calls get_event for details
4. Agent calls a scoped alert tool (Discord, Slack, PagerDuty, etc.) with structured fields

Custom URL vs provider sources