EventPerson Mapping
An EventPerson ingest creates or updates a person in an event from a JSON payload — usually a webhook from your CRM. A field map lists rules; each rule reads a value from your payload (keyMatch) and writes it to a Jomablue field (type). The person is identified by organisation_uid: a match updates the existing person, otherwise a new one is created. Anything in the payload that no rule references is ignored.
The mapping
The fields
Identifier and text fields. organisation_uid is the person's unique ID in your system — it decides update-vs-create, so use something stable like a CRM contact ID. first_name, last_name, job_title, company, and email are straight copies from the payload path in keyMatch.
mobile. Numbers are stored in international E164 format. With mobileCountry pointing at a country field, local formats are converted automatically — 0402 222 111 with AU becomes +61402222111. Country accepts codes like AU/AUS. Without mobileCountry, the number must already start with +.
category. Each rule fires when the payload's category field equals its valueMatch, and assigns the matching mapToId:
category value | Category ID |
|---|---|
Delegate | 1 |
Sponsor | 2 |
Speaker | 3 |
Staff | 4 |
VIP | 5 |
Categories are additive here: assigning one leaves any categories the Person already has in place. That's the difference from the advanced version, which removes the other roles when it assigns one. If no Category is assigned, the event's default Category is applied.
Note: The IDs 1–5 are placeholders. Use your event's real category IDs, and set valueMatch to the strings your system actually sends.
custom_field. The wildcard rule takes every key/value pair inside the payload's custom_fields object and stores each as a custom field, reusing the payload's own keys. Use snake_case keys. Custom Fields must always be a string value, booleans are not accepted.
Note: if a custom_field wildcard mapping is used, then the custom_field object must be included in the payload, even if it is empty.
Worked example
Payload:
Result: a person CRM-10432 (created or updated) named Jordan Avery, Head of Partnerships at Northwind Labs, email as given, mobile +61402222111, category Speaker (ID 3) added, plus custom fields dietary_requirements = Vegetarian, tshirt_size = L, and attending_dinner = true
Validation
You can validate the payload before it's mapped. A payload that fails is rejected before anything is created.
required fields must be present (the identifier and the names needed to create a person). nullable fields are only checked when present. The in: rule limits category to the five known roles, catching typos before they map to nothing. Match the keys to your payload, and update the in: list to your own values.
Other available fields
EventPerson also supports cancelled, item, and program_member. See the full Ingest Endpoints reference for those.