SHVYA AI
Book a call ↗
☰
Features ↗Pricing ↗SHVYA Services ↗SHVYA Product Suite ↗Integrations ↗Documentation ↗ Blog ↗ Login
Skip to documentation content
SHVYA Docs Dashboard ↗
Go to workspace

JustDial lead integration

Request a private JustDial webhook and activate lead push through the advertiser account.

SHVYA product documentation

Setup roles

For JustDial, an organization admin can request setup, but only SHVYA Superadmin can provision or rotate the organization-scoped webhook and choose its destination pipeline/stage.

Activation steps

  1. Open Connect Hub → JustDial and choose Request JustDial Setup.
  2. SHVYA Superadmin reviews the organization request and selects a valid pipeline and active stage.
  3. Superadmin generates the private inbound URL. The organizational contact receives that exact URL through an authorized channel.
  4. Share the endpoint with your JustDial account manager/support and ask them to configure the advertiser's CRM lead-push callback using JSON POST for the supplied Postman format, or GET if that advertiser account requires query parameters.
  5. Ask the provider to send one test enquiry.
  6. Confirm the SHVYA JustDial event log, normalized phone, matching CRM lead and source/stage mapping.

Data behavior

Incoming field names may vary by account; SHVYA uses conservative source mappings. SHVYA accepts application/json POST, form POST and GET, maps state to justdial_state, and normalizes a 10-digit Indian mobile as +91. A subsequent enquiry from the same normalized phone updates existing JustDial attributes without moving a progressed lead backward in its pipeline. A replay of the same leadid is idempotently acknowledged. A JustDial lead does not automatically authorize a WhatsApp welcome message.

If nothing arrives

Check that Superadmin generated an active URL, JustDial actually configured the callback, the provider used the requested method, and the first event was accepted. An accepted lead receives HTTP 200 with plain text SUCCESS. Paused or invalid routing returns HTTP 503. Verify the specific event status and matching CRM lead rather than relying only on the provider's SUCCESS message. Request a redacted provider sample if their payload differs.

Security

The full callback URL includes a secret token. Treat it as a credential. Rotating the URL invalidates the old callback; the advertiser must update its configuration.

Integration debugging · CRM lead records.

Still need help with this?

Open a support ticket with the affected feature, what happened and a safe error reference.

Contact support ↗

More in Connect Hub & Integrations