Universal Webhook Mapper

Universal Webhook Mapper (UWM) turns compatible external webhook payloads into lead data. Use it when a sender can push HTTP events but cannot format them like Convertly’s Inbound Leads API.

UWM is an inbound mapper, not a universal two-way synchronization service. Tools requiring polling, OAuth, or unsupported authentication may need a dedicated integration.

Choose a connection

Open Integrations → Universal Webhook Mapper as a workspace Admin.

Available recipes include Generic JSON, Tawk.to, Justdial, Housing.com, Magicbricks, 99acres, and Sulekha. A recipe is a starting mapping, not a guarantee that every account or payload variant from that provider is compatible.

Create and authenticate a source

1. Choose a recipe and a recognizable source name.
2. Set the relevant lead defaults and new-lead alert recipients.
3. Copy the source-specific URL and the authentication values shown during creation.
4. Configure the sender’s destination and authentication.
5. Send a privacy-safe representative test event.

Generic JSON and supported property-portal recipes require both the secret source URL and the generated x-webhook-secret header. Tawk.to uses its supported provider-signature configuration instead. URL-token-only delivery is not sufficient for a generic source.

Keep full webhook URLs, signing secrets, and header secrets private. Do not put secrets in query strings or screenshots.

Review the mapping

A valid sample helps you map incoming fields to CRM destinations. For example:

Incoming field	CRM destination
contact.name	Lead name
contact.email	Email
contact.phone	Phone
campaign.source	Source or the appropriate attribution field

Use paths from your actual captured sample, not the example paths above. Lead creation/update profiles must resolve at least email or phone.

Review supported transforms, fallback paths, defaults, custom fields, and event profiles. Mapped incoming values take priority; enabled defaults fill supported missing values.

Enable and test

Enable the reviewed source, send a new controlled event, and check the resulting lead. Confirm ownership, contact details, source, categories, and any attribution supplied.

Some events may append related activity, be ignored, or be treated as duplicates according to the configured profile. Not every webhook delivery should create another lead.

Inspect logs

Use View logs on the integration card or setup page. Filter to the relevant source and inspect the result.

• Authentication failed: check the required header or provider signature.
• Sample captured: finish and review the mapping.
• Validation failed: inspect required identity fields and supported values.
• Duplicate or ignored: check the event identity and profile.
• Success: confirm the intended lead or activity in the CRM.

For a sender that can construct Convertly’s native payload, use the Inbound Leads API.