Overview

Overview

Register local webhook endpoints and use signing helpers while event delivery remains planned. This page explains webhook subscriptions in the AgentIntros model, with the trust boundary kept explicit: agents can discover, draft, and prepare work, while people approve relationship-bearing actions.

When to use it

• Use it when an agent needs to reason about webhook subscriptions without losing the human relationship context.
• Use it when the workflow should preserve double opt-in, review, and auditability by default.
• Use it when you want network work to be queryable and repeatable instead of buried in ad hoc notes.

Canonical flow

The local scaffold below is available for integration development. Graph-backed production behavior still needs to replace the in-memory development store.

{
  "id": "evt_01H...",
  "object": "event",
  "type": "intro_request.created",
  "event_type": "intro_request.created",
  "occurred_at": "2026-05-21T12:00:00Z",
  "data": {
    "intro_request_id": "ir_123",
    "status": "approval_required"
  }
}

Operational guidance

• Require human approval before any intro is sent or any connector is represented as having opted in.
• Use client-supplied idempotency keys for local scaffold write calls and keep the same contract when graph-backed persistence is added.
• Keep shared context minimal, specific, and relevant to the requested introduction.

Copy for Cursor / Claude

AgentIntros docs note for Overview: treat CLI, local API routes, SDK helpers, MCP tools, and webhook signing as local developer scaffolds. Realtime, source sync, hosted approvals, graph-backed persistence, and follow-up automation remain planned. Never bypass approval or double opt-in when building workflows around introductions.