Lead capture integrations

IndiaMART CRM integration that puts buyers on a rep's list

Our IndiaMART CRM integration needs one thing: the CRM key from your IndiaMART seller account, pasted once. DigiPix Flow then collects your buyer enquiries on a schedule, skips the ones it already has, and turns each new one into a lead with the buyer's name, mobile, email and company, routed to a rep who can call while the buyer is still comparing quotes.

  • Connected with your IndiaMART CRM key
  • Repeat enquiries skipped by query ID
  • Routed to a rep by your own rules
An example of the DigiPix Flow Leads screen while an IndiaMART sync lands. The IndiaMART chip on the capture bar resets to last synced just now and a new enquiry from Deepak Kulkarni about a milk storage tank opens at the top of the list; a repeat enquiry from the same sync is skipped because its query ID was already collected; an assignment rule gives the lead to Neha Patil with a follow-up task; and Neha calls the buyer, moving the lead to Contacted.
shortest gap between checks, IndiaMART's own limit
5 min
of enquiries collected on the first sync
24 hours
the furthest back IndiaMART lets any sync reach
7 days

What comes across with every IndiaMART enquiry

  • IndiaMARTEnquiries from your seller account
  • BuyerFirst and last name, split for you
  • MobileFormatted with +91 for matching
  • CompanyThe buying business, when given
  • EnquiryProduct, message and city on record
  • Query IDIndiaMART's own reference, kept once
THE PROBLEM

Where IndiaMART enquiries slip through

See how it's fixed
  1. Enquiries that sit in one more panel

    Buyer enquiries sit in the IndiaMART seller panel while the rest of your sales work happens somewhere else. Someone has to remember to open it, and the enquiry that arrived at lunch is found at five, after the buyer has already taken calls from other suppliers.

  2. Copying buyers into a spreadsheet by hand

    A coordinator copies names and numbers from Lead Manager into a sheet each morning. Digits get swapped, the product the buyer asked about is left out, and a rep calls a number that was typed wrong — or never calls because the row was missed.

  3. The same enquiry handled twice

    When two people copy from the same panel, one enquiry becomes two rows and two reps call the same buyer. It wastes both reps' time and tells the buyer your team does not talk to each other, just as they are deciding who to trust.

CONNECT

Connect with the CRM key from your seller account

Your IndiaMART seller account has a CRM key for connecting a CRM like DigiPix Flow. Paste it into the IndiaMART connector on the Integrations page, test it, and save. DigiPix Flow asks IndiaMART whether the key works before connecting, refuses a key IndiaMART rejects, and stores it encrypted, showing only its last four characters. If IndiaMART is busy at that moment, the key is saved and confirmed on the first sync.

  • One field: the CRM key, known as glusr_crm_key
  • Test connection before you save
  • A key IndiaMART rejects is never saved
  • Stored encrypted, with Rotate credentials to replace it
An example of the IndiaMART connector on DigiPix Flow's Integrations page: a Credentials card with one field, CRM key (glusr_crm_key), filled with a hidden key, Save & connect and Test connection buttons, a confirmation that IndiaMART verified the key, and, below, the saved state showing only the key's last four characters with a Rotate credentials button.
COLLECTION

IndiaMART leads to your CRM, on a schedule IndiaMART allows

IndiaMART lets each key be asked for enquiries once every five minutes, so DigiPix Flow checks on a schedule rather than waiting to be told. The connector starts at every 15 minutes and can be set as close as every five. The first sync reaches back 24 hours, and where each sync finished is saved, so the next one picks up from there without gaps.

  • Every 15 minutes to start, as often as every five
  • The last 24 hours collected on the first sync
  • Progress saved after every sync, so nothing is skipped
  • A five-minute wait whenever IndiaMART asks for one
An example of the IndiaMART connector's sync settings in DigiPix Flow: the frequency is set to every 5 minutes, the shortest IndiaMART allows, with a note that it starts at every 15 minutes; below, a sync timeline shows the first sync looking back 24 hours and bringing in 11 enquiries, then syncs at 10:05, 10:10 and 10:15 each starting from the point the last one saved.
WHAT ARRIVES

The buyer's details, on a lead your team can work

Each enquiry becomes a lead with the buyer's first and last name, email, company and mobile number, which is rewritten with +91 so it matches the same person arriving from another channel. The rest of what IndiaMART sends — the product, the category, the buyer's message, their city, state and pincode, and the time they asked — is saved with the lead's source record.

  • Name split into first and last name
  • Mobile numbers formatted as +91 for matching
  • Email and company filled in when the buyer gives them
  • Product, message, city and enquiry time kept with the source
An example of an IndiaMART enquiry becoming a lead in DigiPix Flow: on the left, what IndiaMART sent for Deepak Kulkarni of Kulkarni Dairy Equipment, with a 10-digit mobile number; on the right, the lead with first name Deepak, last name Kulkarni, mobile +91 98220 41376, email and company filled in and IndiaMART as the source; below, the product, message, city and enquiry time saved with the lead's source record.
NO REPEATS

One enquiry, one lead, however often you sync

Every IndiaMART enquiry carries its own query ID, and DigiPix Flow remembers each one it has collected. When a sync window overlaps the last one, the enquiries it already has are skipped rather than added again. A buyer who sends a fresh enquiry is a different matter: that new lead is checked against your existing leads by email and phone, and a match is flagged for someone to review.

  • Each enquiry recognised by IndiaMART's query ID
  • Overlapping sync windows never create a second lead
  • New enquiries checked against existing leads
  • Matches flagged for review, never combined for you
Explore duplicates
An example of an IndiaMART sync in DigiPix Flow whose window overlaps the previous one: of three enquiries returned, two with query IDs already collected are skipped and one new enquiry from Rahul Kumar becomes a lead; below, a separate new enquiry from Amit Mehta matches an existing lead by phone and is flagged as a likely duplicate with a Review button, not combined.
ROUTE & RESPOND

The right rep calls the buyer first

IndiaMART leads go through the same pipeline as every other lead. Assignment rules can pick them out by source and share them round robin or by workload, respecting working hours, with a default owner when no rule matches. The lead is scored, the rep gets a follow-up task, and response timers raise an alert if the buyer is left waiting too long.

  • Assignment rules that can match IndiaMART as the source
  • Working hours respected, with a default owner as fallback
  • Scored on arrival, so the likeliest buyers stand out
  • Response timers that alert when a buyer waits
Explore the lead inbox
An example of DigiPix Flow's assignment rules with an IndiaMART rule first, sharing IndiaMART enquiries round robin between Neha Patil and Rahul Kumar within working hours, a second rule for website and Meta leads, and a default owner, Amit Mehta, when no rule matches; below, Deepak Kulkarni's IndiaMART lead is assigned to Neha Patil within a minute, with a call task and a 30-minute first-contact timer running.
SOURCE

IndiaMART lead management beside every other source

Every lead from IndiaMART carries IndiaMART as its source, so it can be filtered on the leads list and compared with Meta, Google, your website and imports in your reports. At the top of the leads list, IndiaMART has its own capture chip with a count of new enquiries and when it last synced, so you can see at a glance that it is working.

  • IndiaMART set as the source on every lead
  • Filter the leads list to IndiaMART enquiries only
  • Compare IndiaMART with your other sources in reports
  • A capture chip with new enquiries and the last sync
Explore reports
An example of IndiaMART as a lead source in DigiPix Flow: the leads list's capture bar shows 4 new from IndiaMART BuyLeads, last synced 3 minutes ago, beside 6 new from Meta Lead Ads, with the list filtered to the IndiaMART source; below, a leads-by-source report for September shows IndiaMART with 48 leads next to Website with 36, Meta Lead Ads with 31, Google Ads with 17 and Import with 9.
HEALTH

Know the moment collection stops working

The connector shows whether it is healthy and when it last synced. If a sync fails, the reason is kept on the connector, and DigiPix Flow waits longer between each retry, up to six hours, rather than hammering the key. Admins are told when a sync gives up. Retry by hand once it is fixed, or pause the connector without disconnecting it.

  • Healthy or degraded, with the time of the last sync
  • The error kept on the connector when a sync fails
  • Retries spaced further apart, up to six hours
  • Retry sync or pause, without losing the connection
An example of the IndiaMART connector's health in DigiPix Flow: a degraded status with the last successful sync at 13:35 and the failure reason kept on the connector, a Retry sync button, retries spaced 10 and then 20 minutes apart until a sync at 14:10 succeeds and brings in 3 new enquiries, and a note that admins are told when a sync gives up.
HOW IT WORKS

From a CRM key to a call with the buyer, in five steps

  1. STEP 01

    Paste your CRM key

    Add the key from your IndiaMART seller account and test it.

  2. STEP 02

    Enquiries are collected

    DigiPix Flow checks for new buyer enquiries on your schedule.

  3. STEP 03

    Repeats are skipped

    Enquiries it already has are recognised by their query ID.

  4. STEP 04

    A rep is assigned

    Your assignment rules give the lead an owner and a follow-up task.

  5. STEP 05

    The buyer gets a call

    Response timers make sure nobody is left waiting.

THE DIFFERENCE

IndiaMART in a CRM vs the seller panel and a spreadsheet

What it coversThe seller panel and a spreadsheetDigiPix Flow
Finding new enquiriesSomeone opens Lead Manager when they rememberCollected on a schedule, as often as every five minutes
Getting buyers into your recordsNames and numbers copied by handName, mobile, email and company filled in for you
Phone numbersTyped in whatever format, sometimes wrongFormatted with +91 so they match other channels
The same enquiry twiceTwo rows and two reps calling one buyerSkipped by IndiaMART's query ID
Who calls the buyerWhoever picks the row from the sheetAssignment rules, with a default owner as fallback
Knowing it has stoppedNobody notices until enquiries dry upHealth, last sync and an alert when a sync fails
Comparing sourcesA separate count kept for IndiaMARTIndiaMART as a source in the same reports
INTEGRATIONS

Other ways leads reach the same list

IndiaMART is one of several ways enquiries reach DigiPix Flow. Leads from ad forms, your website, your own systems and your old lists all land in the same leads list, each with its source.

IndiaMART integration questions, answered

What do I need to connect IndiaMART?

The CRM key from your IndiaMART seller account, sometimes shown as glusr_crm_key, which you will find in your IndiaMART seller account. Paste it into the IndiaMART connector on the Integrations page, press Test connection, then save.

How quickly do IndiaMART enquiries reach DigiPix Flow?

The connector checks every 15 minutes to begin with, and you can set it to every five minutes. Five minutes is the shortest gap IndiaMART allows for each key, so a new enquiry becomes a lead on the next sync after the buyer sends it.

Will I get enquiries from before I connected?

The first sync collects the last 24 hours of enquiries. IndiaMART never lets a sync reach back more than seven days, so if the connector is paused or failing for longer than a week, enquiries older than that will not be collected.

Which details come across from IndiaMART?

The buyer's name, split into first and last name, their email, company and mobile number, formatted with +91. The product, category, message, city, state, pincode, alternate contact details and the time of the enquiry are saved with the lead's source record.

What happens if the same enquiry is collected twice?

It is skipped. Every IndiaMART enquiry has its own query ID, and DigiPix Flow keeps a record of each one it has collected, so overlapping sync windows never produce a second lead for the same enquiry.

What if a buyer I already have sends a new enquiry?

A new enquiry has a new query ID, so it becomes a lead. That lead is then checked against your existing leads by email and phone, and a match is flagged as a likely duplicate for your team to review. Nothing is combined automatically.

Is consent recorded for IndiaMART leads?

No. IndiaMART does not send a consent answer with its enquiries, so DigiPix Flow does not record one. Leads from website forms, Meta, Google and the API can carry consent, but IndiaMART leads arrive without it.

How do I know if the connection has stopped working?

The connector shows whether it is healthy and when it last synced, and the IndiaMART chip on the leads list shows the last sync too. When a sync fails, the error is kept on the connector, retries are spaced out, and admins are notified if it gives up.

Can I route IndiaMART leads to particular reps?

Yes. Assignment rules can match on the lead's source, so IndiaMART enquiries can go to one person, round robin across a team or to whoever has the fewest open leads, respecting working hours, with a default owner if no rule matches.

Something we haven't covered? Talk to an expert

Put every IndiaMART enquiry in front of a rep

Talk to an expert — bring your IndiaMART seller account and the way your team handles enquiries today, and see them arrive as leads.

  • A real person, not a bot
  • Bring your IndiaMART account
  • See enquiries become leads
Talk to an expert