Events
The local event catalog used by Agent Intros webhook signing and endpoint registration.
AgentIntros is CLI-first today with local API, SDK, MCP, and webhook scaffolds for integration development. Graph-backed production behavior is still separate from these local routes.
Overview
The local event catalog used by Agent Intros webhook signing and endpoint registration. This page explains webhook event names and payloads 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 event names and payloads 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"
}
}Reference
| Event | When it fires |
|---|---|
| intro_request.created | A request enters the graph. |
| intro_request.matched | Warm paths are scored and attached. |
| approval.requested | A human is asked to approve the intro. |
| approval.approved | The human approves the trust-bearing step. |
| approval.declined | The request is blocked or sent back for changes. |
| intro.drafted | A draft is ready for review. |
| intro.sent | The approved intro is sent. |
| followup.scheduled | A follow-up is placed on the timeline. |
| followup.due | The follow-up needs attention. |
| followup.completed | The loop is closed with an outcome. |
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 Events: 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.