Direct API
Use API endpoints for inboxes, contacts, messages, files, workflows, approvals, and events.
Ready View API indexIntegrations
Not a rigid connector marketplace. Practical connection primitives.
Core integration paths
Start in one of two ways: copy the Gent address into To/CC on an existing thread, or connect via a scoped API token. Inbound is always live. Response work is drafted and held for review.
Use API endpoints for inboxes, contacts, messages, files, workflows, approvals, and events.
Ready View API indexReceive event streams and trigger external actions with guarded request signing and event filtering.
Ready Webhook detailsShip tested TOML-based workflow examples for faster setup across recurring use cases.
Ready Open workflow libraryRun recipe payloads from your own scheduler or backend with your own secrets and logging.
Ready Recipe referenceUse Gent as your governed email layer for agent workflows, then connect clients like Claude, ChatGPT/Codex, Hermes, OpenClaw, or your own copilots.
Ready See agent-ready workflowsCommon stacks
Push normalized events, route triage outcomes, and keep human tasks aligned with internal queues.
Use webhooks + workflow actions to bridge each step.
Attach email intake to invoice workflows, approvals, and payment-state updates through API calls.
Keep external documents in external tools; keep source email controls in Gent.
Use actions to sync key event states for lightweight tracking and reporting across teams.
Minimal fields, high predictability, explicit governance.
Integration plan
Start with one inbox, one receive path, and one review path. Expand only after logs and approvals show stable behavior under real workload.
Read docs for integration requirements