We plug into what you already run
No rip and replace. No new CRM. emaze.ai listens to the system your team already works in, sends through the channels your customers already recognise, and writes every interaction back to the record it came from.
Leading integrations
Built to connect
An integration here is configuration, not code.
One OAuth engine, every provider
Authorization code, client credentials, signed assertion - every OAuth 2.0 provider authenticates one of these ways, and one engine handles all three.
A new system is a configuration record
Register, configure, connect. Typically a day or two. No deployment, no release cycle.
Secure and self-maintaining
Credentials encrypted before they touch a database, tenants isolated by schema, least-privilege scopes. Tokens renew themselves ahead of expiry.
The question is not "do you integrate with X?" It is "how soon do you need it?"
If it has an API, we connect to it
Any system that can send a POST and receive JSON can drive emaze.ai. If it has an API, we connect to it - including the ones you already run:
CRM
- Salesforce
- HubSpot
- Microsoft Dynamics
- Zoho
- Pipedrive
- monday CRM
- Zendesk
- Freshsales
- SugarCRM
- Close
- and yours
Marketing automation
- Braze
- Klaviyo
- Marketo
- ActiveCampaign
- Mailchimp
- Iterable
- Customer.io
- Omnisend
- Dotdigital
- MoEngage
- and yours
CDP and data
- Segment
- mParticle
- Tealium
- BigQuery
- Snowflake
- Amplitude
- Mixpanel
- RudderStack
- Databricks
- and yours
Messaging and delivery
- Twilio
- WhatsApp Business
- SendGrid
- Brevo
- Commbox
- Mailgun
- Postmark
- Infobip
- Vonage
- and yours
The API
Plain REST under one base URL, standard methods, standard status codes, JSON in and out. One POST creates the touchpoint and hands back the link; even a spreadsheet can drive it.
One POST in, a link out
Send an event with the record you want personalized. You get back the touchpoint URL, a ready-to-send message built from the same parameters, and the response of every downstream call.
Speaks whatever your system speaks
Plain REST and JSON, with form-data and urlencoded endpoints for systems that cannot send JSON. Standard methods, standard status codes, predictable URLs.
Reads your data, writes it back
Search and autocomplete against your own tables, pull record details in, then report events and update records when the touchpoint goes out. Unlimited endpoints per operation.
Lives inside your CRM
A create-window endpoint opens the emaze.ai builder inside your own system as a popup, pre-filled from the record on screen.
Keys you control
API keys are created in your account, scoped to a user or a team, extendable and revocable at any time. Keys are never stored where they could be recovered.
Multilingual delivery with full RTL
RTL and LTR rendered properly rather than mirrored, in production today.
Behind the scenes
The whole integration is three moments on the wire.
- POST
Create the PRP
Your system posts the touchpoint id, your key, and the parameters of one record.
POST /api/prp/create X-Api-Key: emz_live_•••• { "touchpoint_id": "tp_8Ma2K", "recipient": { "first_name": "Dana", "vehicle": "Hybrid SUV", "branch": "North", "language": "en" } } - 200
The server answers with the link
One response: the personalized response page URL and a ready-to-send message.
HTTP/1.1 200 OK { "url": "https://emaze-ai.com/p/aX93kQ", "message": "Dana, your Hybrid SUV is ready. Pick a slot at North: https://emaze-ai.com/p/aX93kQ" } - POST
Engagement writes back
Every interaction returns to the endpoint you agreed - as it happens.
POST https://crm.yourbrand.com/emaze { "prp_id": "aX93kQ", "recipient_id": "crm_51392", "event": "form_submitted", "active_seconds": 47, "scroll_depth": 0.9 }
Frequently asked questions
Do we need to replace our CRM?
No. emaze.ai listens to it and sends through it.
What if my system is not on the list?
It does not need to be. Anything that can send a POST and receive JSON can drive emaze.ai, and a new OAuth provider is a configuration record on our side - typically a day or two, not a development project.
Do we need to develop anything?
No. On Shopify and DriveCentric we listen to webhooks and run the whole journey with zero development on your side. Everywhere else, your system sends a POST with the record and gets the link back; engagement returns to an endpoint you already have.
How do touchpoints reach customers?
As a link over WhatsApp, SMS or email, through the sending identity your business already uses. We do not become a new sender your customers do not recognise.
What comes back to my stack?
Every open, scroll, click, swipe, dwell-second and form submission returns to the CRM record as activity, and a daily aggregate lands in your BI, one row per record.
How is personal data handled?
Analytics stores declared dimensions only; personal fields are excluded from the event store by design. SOC 2 Type II audited, report available under NDA. GDPR compliant.
What happens to the data
The first question every security reviewer asks, answered before they ask it.
Analytics stores declared dimensions only. Personal fields are excluded from the event store by design.
SOC 2 Type II audited, report available under NDA.
GDPR compliant.
Passed enterprise third-party vendor reviews, including a full remediation cycle.
