For builders

Connect product events without losing the human context.

Use the public design previews to understand how product email, customer data, and agent-assisted work are intended to fit together.

A public production API, hosted MCP connector, and working credentials are not offered by this site yet.

Choose the connection you need.

Each path has a different permission boundary, delivery model, and failure mode.

Product email
Explore idempotent requests, recipient checks, retries, and the difference between accepted and delivered.
Read the API design
Customer data
See which connected tools could share events and fields, and how do-not-send decisions should survive sync.
Explore integrations
AI-assisted work
Preview the proposed MCP boundary for drafting, review, permission, and activity history.
Explore MCP

The most important integration behavior happens after a timeout, a duplicate event, or a change in permission.

Retries are not new actions
A retry should preserve the original intent and not send a second message.
Read the note
Webhooks are evidence
A callback reports an observation; it is not a guarantee that every downstream state is already reconciled.
Read the note
Scoped access
Keep credentials, approval authority, and customer data inside clear boundaries.
Review security

The next step

These pages explain intended behavior; public integration credentials and a complete API reference will be published only when qualified.