CRM integration for every accepted lead
Every accepted request fires a signed webhook the instant it happens, ready for you to push into HubSpot, Salesforce, Pipedrive, Zapier, Make or any other tool your team uses. No exports, no manual work, and no CRM-specific connector to wait for.
The difference with a bare-bones webhook is what comes along. With OXIAE, provenance (source, campaign, label) and the full consent proof (text, timestamp, IP) do not arrive as a loose note, but as structured fields in every event and API response: ready to filter, report on and audit inside your own CRM.
And because you build the mapping yourself, your CRM's own duplicate and validation rules apply exactly as they always do. Nothing sidesteps the rules you already trust.
What you get, built your way
A connection that only passes through contact details leaves half the value on the table. OXIAE's webhooks and REST API carry the full context along, so whatever you build sends sales and compliance teams the same complete lead.
Leads go out in real time
No exports, no copy-paste. Every accepted request fires a signed webhook the moment it happens, ready for your own integration to push into your CRM.
Provenance & consent in every payload
Source, campaign, label and the full consent proof (text, timestamp, IP) are part of every webhook event and API response: structured data, not a loose note, ready to map into any field you choose.
Your CRM stays yours
You decide how a lead becomes a contact, a deal or a record. Because you build the mapping yourself, your CRM applies its own duplicate and validation rules exactly as it always does.
Demonstrable down to the lead
Because provenance and consent arrive as structured fields, you can filter, segment and prove inside your own CRM where every lead came from.
One open interface, connect anything
OXIAE does not sell a native, pre-built connector per CRM. Every accepted lead is available through the same REST API and signed webhooks, so you can push it into HubSpot, Salesforce, Pipedrive, Zapier, Make or any other tool exactly the way your team works.
Open REST API
Pull leads, statuses and consent records on demand. One documented, consistent data model for every request.
Signed webhooks
Every accepted lead fires an HMAC-signed webhook in real time, so you can verify it genuinely came from OXIAE before you process it.
Realtime events
No polling, no batch exports. Your endpoint receives the event the moment a request is accepted and routed.
Full payload
Contact details, provenance and the complete consent proof travel together in a single event, ready to map into any system.
A few examples of what teams build on top of this: creating a Contact and Deal in HubSpot, writing a new Lead in Salesforce, adding a Person and Deal in Pipedrive, or triggering a Zapier or Make scenario that fans out to a dozen other tools. In every case, you choose the objects, the field mapping and the duplicate handling, using each tool's own API and its own rules.
This is what a webhook event looks like
This is the payload OXIAE sends to your webhook endpoint, and returns via the API, on every accepted request. Note the provenance and consent blocks: those are included by default, ready for you to map into your own CRM.
# Example: webhook payload OXIAE sends for every accepted lead
{
"id": "lead_8f21",
"status": "accepted",
"contact": {
"name": "Sanne de Vries",
"email": "sanne@example.com",
"phone": "+31 6 12345678"
},
"provenance": {
"source": "google-ads",
"campaign": "legal-aid-q2",
"label": "legal-desk"
},
"consent": {
"given": true,
"text": "I consent to being contacted.",
"timestamp": "2026-03-12T09:41:07Z",
"ip": "84.12.x.x"
}
}How you connect your CRM
From your first API key to live in five clear steps. You always start in a sandboxed environment and only go live once you have seen the result in black and white.
Get API access
Generate a scoped API key and a webhook signing secret from your OXIAE dashboard. You decide what it can read, and you can revoke it at any time.
Subscribe to events
Point a webhook endpoint at your own integration, or poll the REST API. Choose which events matter to you: accepted, rejected, updated.
Map the fields yourself
Decide how the OXIAE payload lands in your CRM: which object, which pipeline, which field carries the provenance and consent data. You are in control of the mapping.
Test in the sandbox
Send test leads through your integration and check in your own CRM that everything lands the way you intended, before real data flows.
Go live
Happy with the result? Switch your integration to production. From that moment leads flow through in real time, with retries and a full audit trail as a safety net.
Provenance & consent travel in every payload
With OXIAE, consent is not a free text field or an afterthought checkbox. The consent proof is captured at the moment of the request and included as structured data in every webhook event and API response, so you can map it into your own CRM and demonstrate that every lead has valid consent.
Captured at the source
Consent text, timestamp and IP are recorded on the form or landing page, before the lead ever reaches your integration.
Included in every payload
Every webhook event and API response carries consent.text and consent.timestamp as structured fields, ready for you to map into your own CRM.
Covered by the audit trail
Outside your CRM, OXIAE keeps a full audit trail: what was processed and delivered, when, by whom and on what basis.
Three ways to build your connection
HubSpot, Salesforce, Pipedrive or anything else: there is no per-CRM connector to pick from. Instead there are three routes, each carrying the same provenance and consent data.
REST API & webhooks
Build the integration yourself on a clear REST API with signed webhooks. Full control, your data model.
API & webhooksZapier / Make
Point Zapier or Make at our webhooks and route leads into virtually any CRM or tool, no code required.
Zapier / MakeCustom integration
A legacy CRM or your own data warehouse? We build a tailored integration into your platform.
Custom integrationFrequently asked questions about CRM integrations
The questions we get most often from teams connecting their CRM to OXIAE.
Do you map consent directly into my CRM?
Not automatically into a specific CRM: OXIAE does not write into HubSpot, Salesforce or Pipedrive for you. What we do guarantee is that every accepted lead carries the full consent proof (the verbatim text, the timestamp and the IP address) as structured fields in every webhook event and API response. You map those fields into whichever CRM field you choose.
Does my CRM stay clean with duplicate leads?
That depends on how you build your integration. OXIAE does not write into your CRM directly, so your CRM's own duplicate rules apply exactly as they do for any other integration you build: most teams dedupe on email using their CRM's native matching logic when they process our webhook events.
What happens to my validation rules and required fields?
They apply exactly as they always do. Because you build the connection between OXIAE and your CRM yourself, using the REST API or webhooks, your CRM's own validation rules and required fields are enforced by your CRM, not bypassed or pre-filled by us.
Do you support two-way sync?
OXIAE is built for outbound delivery: signed webhooks and REST API responses push lead data out in real time. Status updates back toward OXIAE, for example marking a lead as contacted, are possible by calling our API from your side, but that is something you build as part of your own integration.
Which CRM systems are supported?
Any system that can receive a webhook or call a REST API works: HubSpot, Salesforce, Pipedrive, a system connected via Zapier or Make, a data warehouse, or anything else you use. We do not offer a native, pre-built connector for any single CRM. Instead you get one open, documented interface that works everywhere.
How quickly does a lead arrive in my CRM?
The webhook itself fires in real time: as soon as a request is accepted and routed, OXIAE sends the event. How quickly it then lands in your CRM depends on your own integration. If your endpoint is briefly unavailable, we retry delivery with exponential backoff, so nothing gets lost.
How long does it take to set up an integration?
Generating an API key and receiving your first webhook event usually takes minutes. Wiring that into your CRM, mapping fields and testing in the sandbox depends on your own build; most teams are live within a day. Want us to build it for you instead? Ask about a custom integration.
Connect your CRM, your way
Book a demo and see how leads go out in real time, with provenance and consent in every payload and a full audit trail.