EmailEngine exposes every email account it manages through one REST API and one webhook stream, so an integration is HTTP and JSON whatever the application on the other side. The pages in this section cover the environments that need more than a plain HTTP client.
Integration Guides
| Guide | What it covers |
|---|
| PHP Integration | The published PHP SDK, postalsys/emailengine-php, and the calls it does not cover |
| CRM Integration | Keeping a CRM's activity timeline in step with a mailbox: account onboarding through the hosted form, message sync from webhooks, sending as the CRM user |
| Low-Code Integrations | Zapier, Make and n8n: receiving webhooks, calling the API, and reshaping payloads with webhook routes |
| OpenAPI Specification | The document every instance publishes, for generating a typed client in any other language |
| Feature | What it covers |
|---|
| MCP for AI Agents | The opposite direction from an integration: an AI client such as Claude Code or Cursor calls EmailEngine directly, through the Model Context Protocol endpoint and a narrowed access token |
| AI Processing | EmailEngine calling a model itself, to attach a summary, sentiment and risk score to each new message's messageNew webhook |
| Webhook Routes | Sending different events to different endpoints, with filter and map functions, when one receiver is not enough |
See Also