Learn how to send data from external systems into myne using webhooks, and map that data to customer profiles, events, and more.
Webhooks allow myne to act like a lightweight CDP — receiving real-time data from your other tools and turning it into structured customer records and activity. Once ingested, this data can power groups, automations, and insights across your account.
Who is this for?
If you already collect data in another system (Another CRM, your app backend, or a SaaS platform), you can send that data into myne via a webhook.
Instead of keeping your customer data siloed, myne can:
Build and update customer profiles
Track activity (events like page views, signups, purchases)
Store product, transaction, or business data
Send powerful customer-centric marketing campaigns based on real behaviour
Power automations based on behaviour
In short, anything that can send JSON can be mapped into myne.
How it works (high level)
Most systems send events in a structured format.
For example:
customer→ updates a customertrack→ logs an eventpage→ records a page view
With myne:
You create a webhook URL
Your system sends events to that URL
myne reads the incoming JSON
You define how each field maps into myne
From there, myne unifies & keeps your customer, product, transaction or business data up to date automatically.
Step 1: Create a webhook
Go to Settings → Webhooks and create a new webhook.
You’ll get a unique Webhook Address — this is where your external system will send data.
Give your webhook a Source name (e.g. crm_data, backend_api, mobile_app).
This is just for internal organisation.
Step 2: Choose your setup (Simple vs Advanced)
Simple (Single topic)
Use this when every request to this URL has the same structure.
Example:
Only sending
customereventsOnly updating customer profiles
In this mode:
One JSON shape
One mapping
One entity type (e.g. Customer)
Advanced (Multiple topics)
Use this when your webhook receives different event types.
For example:
customer→ update customertrack→ log eventpage→ track page view
Instead of creating multiple webhooks, you can use one URL and route events based on a field (typically type). If you want to map each topic to a different URL use the simple setup
Step 3: Map incoming data
This is where you tell myne how to read your data.
You’ll map:
Incoming field (JSON path) → myne field
Example:
traits.email→ Emailtraits.firstName→ First Nameproperties.product_name→ Product
You can:
Paste sample JSON in the 'Topic Sample' field
Select fields directly from the payload -
Add multiple mappings - Click Add Row to add as many mappings as you wish
myne will validate required fields before allowing you to save.
Step 5: Test and preview
Use the Preview section to:
Paste sample JSON
Run a test
Confirm mappings behave correctly
Once saved, send real data from your system.
If something looks off, you can:
Load recent payloads
Adjust mappings
Re-test quickly
What this unlocks
Once your webhook is live, myne becomes your central customer layer.
You can:
Build groups based on external behaviour
Trigger automations from product events
Combine POS + product + marketing data
Generate richer insights (Signals)
For example:
“Users who viewed pricing page but didn’t purchase”
“Customers who signed up via app but haven’t returned in-store”
“Top users based on product usage + spend”
Summary
Webhooks allow you to bring external data into myne in real time.
One webhook can handle multiple event types
Data is mapped directly into customer profiles and activity
Works seamlessly with CDP, CRM and internal business tools
Powers segmentation, marketing, automations, and insights
Once set up, myne becomes a true customer data layer across your stack.