IntegrationLiveLast tested 2026-08-27Lead source

Sulekha for Manufacturing

Capture Sulekha service and supplier enquiries into the pipeline so a local enquiry is not lost between an app notification and a callback.

In short

KanchanFlow, the RFQ-to-Order CRM, receives Sulekha enquiries through their lead delivery webhook and creates a deduplicated lead with the requirement text, the buyer's number and the category searched. It is the narrowest of our Indian lead channels and suits shops selling locally rather than nationally.

Start Free Trial (No Credit Card)See a Live Quote Draft

Diagram of the Sulekha integration: fields KanchanFlow writes to Sulekha on the left, fields it reads back on the right.

Who this is for. This connector is for USA manufacturers with India operations, India-based contract customers, or manufacturers exporting to India. Sulekha is a local Indian channel; it has no function for a domestic USA customer base.

Sulekha is a local-intent channel. Its enquiries tend to come from buyers looking for a supplier within reach rather than from procurement teams running a national sourcing exercise. That makes them smaller, closer and quicker to close when they are genuine, and it also makes them easy to lose, because a local enquiry that is not answered today is answered by somebody else tomorrow.

The connector puts those enquiries in the same pipeline as everything else, with the same response clock and the same dedupe rules. The value is not sophistication; it is that a Sulekha enquiry stops being an app notification somebody meant to act on and becomes a lead with an owner.

Status: Live in production
Category: Lead source
Plan availability: All tiers — Starter includes one selectable lead source; Professional and Enterprise include unlimited
Sync cadence: Real time by webhook where your Sulekha plan supports it; otherwise every 15 minutes by poll

Field by field

What syncs, in both directions

These are the actual fields that move. Anything not on these two tables does not sync, and we would rather write that down than let you assume it does.

KanchanFlow → Sulekha

What we write out when a record moves forward.

Field	What we send
Lead acknowledgement	Receipt is acknowledged so the same enquiry is not re-sent on the next delivery cycle.
Nothing else	Listing content, category selection and paid plan settings stay in the Sulekha business panel.
Duplicate suppression key	The Sulekha enquiry ID is stored on the lead to suppress redelivery duplicates.

Sulekha → KanchanFlow

What comes back onto the customer, quote or order record.

Field	What we read
Enquiry text	The buyer's stated requirement, which on Sulekha is usually short and needs a call to qualify.
Buyer name and mobile	The contact set Sulekha exposes; email is often absent.
Category and locality	The category searched and the buyer's locality, used for routing and for judging travel distance on a site-visit job.
Enquiry timestamp	The moment the enquiry was raised, which the response clock runs from.

Sync cadence. Real time by webhook where your Sulekha plan supports it; otherwise every 15 minutes by poll. Every record also carries a Sync now control, and the last successful sync time is shown on the record so nobody works from a number of unknown age.

Figures

What this looks like in the product

We do not ship stock imagery or mocked-up screens. These three figures describe the exact shots a designer must capture from a live workspace, each carrying a visible date stamp and recaptured at every quarterly re-test.

Figure 1 · to be captured

The lead inbox filtered to Sulekha, showing enquiries with locality and response clocks.

Capture date required. Capture from a live workspace with numbers masked in the product. Date stamp required.

Figure 2 · to be captured

A Sulekha lead expanded showing the requirement text, locality and the Convert to RFQ action.

Capture date required. Capture a genuine enquiry. Date stamp required.

Figure 3 · to be captured

The lead source comparison report showing Sulekha alongside the other lead channels by volume and conversion.

Capture date required. Requires real comparative data; do not stage it. Date stamp required.

11 steps

Setting it up

Written for the person who will actually do it, in the order they will do it. Nothing here assumes you have done this before.

1Log in to the Sulekha business dashboard with an administrator account.
2Confirm your plan includes lead API or webhook delivery. Several Sulekha plans deliver leads only to the app and SMS, in which case this connector cannot be used.
3In KanchanFlow, open Settings, Integrations, Sulekha and copy the webhook URL and secret.
4Provide both to Sulekha through their dashboard or, on some account types, through their support team.
5Request a test enquiry and confirm it arrives in the lead inbox.
6Set dedupe on mobile number with normalisation, because Sulekha numbers arrive inconsistently formatted.
7Map Sulekha categories to your product lines, sending anything unmapped to a review queue.
8Set routing by locality if you have territory owners, otherwise round robin.
9Set a short response target. Local enquiries convert on speed more than on price.
10Enable the WhatsApp first-response template if the WABA connector is configured.
11Review a week of live leads before extending the routing rules.

Honest ceilings

What this integration cannot do

Every connector has limits. You will find these in week three whether or not we write them down, so we write them down.

Lead API delivery is not available on every Sulekha plan, and whether yours has it is a commercial question for Sulekha, not something we can enable.
Enquiry detail is thin. A short requirement line, a name, a number and a locality is all that arrives, so every lead needs a qualifying call.
There is no email address in most enquiries, so email nurture is not possible on this channel without asking for it on the call.
This is the lowest-volume and lowest-value channel of the twenty-six connectors we ship, and for most manufacturers it will not justify a paid lead-source slot. We would rather you knew that before enabling it.
No historical backfill. Leads flow from connection forward only.
No campaign or spend attribution is exposed, so return on Sulekha spend cannot be calculated inside the CRM.

From the quarterly re-test

Errors you will actually hit

Each of these was reproduced deliberately during testing. The wording is the error as the system reports it, not a paraphrase.

Error	Likely cause	Fix
No leads arrive after providing the webhook	The plan does not include API delivery, or Sulekha support has not activated it on the account.	Confirm entitlement with Sulekha directly. Until they activate delivery there is nothing to configure on our side.
Numbers arrive with inconsistent formatting and duplicate accounts appear	Sulekha passes numbers sometimes with and sometimes without the country code.	Enable number normalisation in the dedupe settings, then merge the duplicates already created.
All leads land in the review queue	No category mappings are configured.	Map the categories you actually serve. Leave the rest unmapped so irrelevant enquiries stay visible as such.
Response clock shows breaches on arrival	Workspace timezone is not set to the timezone Sulekha timestamps in.	Set the workspace timezone in Settings, General. The connector converts once it knows the target.
Enquiry text is empty	The buyer used a one-tap callback request rather than typing a requirement.	Nothing to fix. Treat these as call-me requests and route them to whoever can ring back fastest.

Questions people ask about the Sulekha integration

For most manufacturers, no. Volume is low and detail is thin. If you are on Starter with one selectable source, spend it on IndiaMART or Meta Lead Ads instead.

Related integrations

JustDial

Capture JustDial leads into the RFQ pipeline with the call recording reference, so a phone enquiry becomes a tracked lead.

IndiaMART Insta & Enquiries

Pull IndiaMART enquiries into the CRM within minutes, deduplicate them against existing accounts, and route them to an estimator.

TradeIndia

Import TradeIndia buy leads and enquiries into the RFQ pipeline, including the export enquiries that matter to overseas suppliers.

Keeping this page true

This connector was last tested end to end on 2026-08-27 against a live sandbox: fresh authorisation, an outbound write, an inbound read checked field by field, and the failure paths above triggered deliberately. It is re-tested every quarter and the date on this page changes when it is. Read how we test integrations, or see what is shipping today.

See a live quote draft built from a real RFQ

Fourteen days, no credit card, sample data pre-loaded. If it does not fit your shop, we will tell you in the first call.