IntegrationLiveLast tested 2026-08-27Lead source

IndiaMART Insta & Enquiries for Manufacturing

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

In short

KanchanFlow, the RFQ-to-Order CRM, pulls IndiaMART Insta enquiries and buy leads through the official CRM Integration API, deduplicates them against existing accounts, and routes each one to an estimator with a response clock running. Speed of first response is the single strongest predictor of conversion on this channel.

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

Diagram of the IndiaMART Insta & Enquiries integration: fields KanchanFlow writes to IndiaMART 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. IndiaMART is where Indian industrial buyers issue enquiries, so it matters if you supply into that market.

IndiaMART leads decay faster than any other source we handle. The buyer has sent the same enquiry to five or six suppliers on the same afternoon, and the first credible reply usually takes the conversation. A lead sitting unread in a shared inbox for four hours is, in practice, a lost lead, and no amount of careful quoting afterwards recovers it.

The connector polls the enquiry API on a short cycle and creates a lead the moment one appears, matched against existing customers by phone and email so a repeat buyer does not become a duplicate account. Territory and product-line rules decide who owns it, and a visible response clock starts immediately.

Status: Live in production
Category: Lead source
Plan availability: All tiers — Starter includes one selectable lead source; Professional and Enterprise include unlimited
Sync cadence: Every 5 minutes during Indian business hours, every 15 minutes otherwise

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 → IndiaMART Insta & Enquiries

What we write out when a record moves forward.

Field	What we send
Enquiry acknowledgement	Where your IndiaMART account supports it, we mark an enquiry as actioned so it does not keep resurfacing in the seller panel after your estimator has picked it up.
Response status	Whether a first response was sent and when, written back so the seller panel and the CRM do not disagree about which enquiries are still open.
Nothing else	We deliberately do not push catalogue, pricing or product listing data to IndiaMART. Your listings stay managed in the IndiaMART panel by whoever owns them.
Duplicate suppression key	The IndiaMART enquiry ID is stored on our lead so a re-delivered enquiry updates the existing lead instead of creating a second one.

IndiaMART Insta & Enquiries → KanchanFlow

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

Field	What we read
Enquiry header	Enquiry ID, date, subject, the product or category enquired about, and the enquiry type, whether Insta, buy lead or direct enquiry.
Buyer contact	Name, company, mobile, alternate mobile, email and city, which is the whole contact set IndiaMART exposes.
Enquiry message text	The buyer's own words, preserved verbatim on the lead, because the phrasing is often the only clue to whether they want one part or a thousand.
Quantity and unit where given	Parsed into structured fields when IndiaMART supplies them, left in the message text when it does not.
Buyer's stated location	City and state, used for territory routing and to work out whether the enquiry is inside your realistic delivery radius.

Sync cadence. Every 5 minutes during Indian business hours, every 15 minutes otherwise. 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 IndiaMART, showing enquiries with their response clocks, the matched existing account where one was found, and the assigned estimator.

Capture date required. Capture with at least one clock in a warning state so the urgency is visible. Date stamp required.

Figure 2 · to be captured

A single IndiaMART lead expanded, showing the verbatim enquiry text, buyer contact block, and the Convert to RFQ action.

Capture date required. Capture with buyer contact details masked in the product. Date stamp required.

Figure 3 · to be captured

The IndiaMART source report showing enquiries received, first-response median and conversion to quote over the last 90 days.

Capture date required. Capture real figures from a workspace with genuine history, or omit the shot rather than fake numbers. 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 IndiaMART seller panel with an account that has administrator rights on the listing.
2Navigate to Lead Manager, then the CRM Integration section, and generate a CRM integration key for your mobile number.
3Note the key exactly. IndiaMART keys are long and are frequently truncated when pasted from a phone message.
4In KanchanFlow, open Settings, Integrations, IndiaMART and enter the key together with the registered mobile number on the IndiaMART account.
5Run the connection test. It fetches the last 24 hours of enquiries read-only and shows you what it found without creating any leads.
6Review the sample and confirm the field mapping, particularly which IndiaMART product category maps to which of your product lines.
7Set the dedupe rule. Matching on mobile number is the default because IndiaMART buyers reuse numbers across enquiries far more than they reuse email addresses.
8Configure routing. Territory by buyer state, product line by enquiry category, or round robin. Round robin is the honest default for shops with one estimator per shift.
9Set the response-time target and the escalation. Thirty minutes to first response with escalation to the sales manager at sixty is what we see work.
10Turn on the WhatsApp first-response template if the WABA connector is live, because the fastest credible reply on this channel is usually a WhatsApp message, not an email.
11Enable live import and watch the first day's leads land before you rely on it.

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.

IndiaMART's API is rate limited and their documented guidance is not to poll more often than every five minutes. We honour that, so a lead can be up to five minutes old when it reaches you.
The API exposes only the fields IndiaMART chooses to expose. Attachments a buyer uploaded in the IndiaMART panel do not come through, and there is no way for us to fetch them.
Historical backfill is limited to the window IndiaMART allows on the key, typically the last seven days. You cannot import years of past enquiries.
Lead quality on this channel is genuinely mixed. A meaningful share of enquiries are traders, resellers and price-shoppers rather than manufacturers, and no amount of routing logic changes that. Plan your estimator time accordingly.
We cannot post replies to a buyer through IndiaMART's own messaging. Responses go out by phone, email or WhatsApp from the CRM.
If the IndiaMART key is regenerated in their panel, our polling fails silently from their side until you re-enter it. We alert on consecutive empty responses, but the first hour can look like a quiet day rather than an outage.

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
Connection test succeeds but no leads are ever imported	The key is scoped to a different mobile number than the one receiving enquiries, common where a business has several IndiaMART logins.	Regenerate the key from the account that actually owns the listing, and confirm the mobile number in the connector matches that account.
Every enquiry creates a new account instead of matching the existing one	Dedupe is set to email matching and IndiaMART buyers frequently submit with different email addresses.	Switch dedupe to mobile number as the primary key with email as a secondary. Then merge the duplicates already created from the account list.
Leads arrive with the message text truncated	The buyer's enquiry exceeded the length IndiaMART returns through the API.	Open the enquiry in the IndiaMART panel for the full text. We show the truncation marker rather than silently presenting a partial message as complete.
Import stopped after a burst of enquiries	The API rate limit was hit, usually because a manual re-sync was run alongside the scheduled poll.	Wait for the next cycle. Do not run repeated manual syncs; they consume the same quota the scheduled poll needs.
Duplicate leads appear for one enquiry	IndiaMART re-delivered the enquiry with a new ID after the buyer edited it.	Merge the leads and set the fuzzy dedupe window to one hour, which catches re-delivered enquiries from the same number about the same product.

Questions people ask about the IndiaMART Insta & Enquiries integration

Within five minutes during Indian business hours. That is the fastest IndiaMART's own rate guidance permits and we do not pretend otherwise.

Related integrations

JustDial

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

TradeIndia

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

WhatsApp Business API (WABA)

Send quotes, follow-ups and production updates on WhatsApp from the CRM, with every thread attached to the RFQ it belongs to.

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.