Connect your lead sources to LumaKol

List where your enquiries come from

Before adding anything, write down every place enquiries reach you today: ad forms, marketplaces, portal emails, website forms, payments and the apps you already automate. Integrations → Lead sources → Add source groups the sources the same way, and its search box finds one by name.

• Ads: Google Ads lead forms
• Marketplaces and portals: IndiaMART, JustDial, TradeIndia, and lead emails from portals such as 99acres, MagicBricks and Housing.com
• Website and forms: Google Forms, WordPress, Typeform, Tally, Jotform, Webflow, Wix, Unbounce, and Website or other app for anything else
• Payments and stores: Razorpay, Instamojo, Shopify
• Automation tools: Zapier, Pabbly Connect, Make
• Already in LumaKol, with no outside account: hosted lead forms, website chat and CSV or Excel import

Know the four ways a source connects

Every source reaches LumaKol in one of four ways, and the way decides how fast leads arrive and where you finish the setup.

• Pulled: LumaKol asks the marketplace for new enquiries on a timer. IndiaMART and TradeIndia
• Pushed: the service posts each lead to a private URL the moment it happens. Google Ads, JustDial, every form tool, Razorpay, Instamojo and Shopify
• Forwarded: your mailbox forwards the lead emails a portal sends you to a private LumaKol address. 99acres, MagicBricks, Housing.com and any other portal that emails leads
• Relayed: an automation tool picks the lead up from another app and posts it to LumaKol. Zapier, Pabbly Connect and Make, including Facebook and Instagram lead ads

Pulled sources: IndiaMART and TradeIndia

You paste your marketplace details into the source once, and LumaKol fetches new enquiries from then on. The details are stored encrypted. A new source also picks up the previous day’s enquiries, so nothing that came in during setup is missed.

• IndiaMART: generate the CRM key in Seller Panel → Lead Manager → CRM integration and paste it with Edit. LumaKol checks every 5 minutes, which is as often as IndiaMART allows per key
• TradeIndia: copy the User ID, Profile ID and Key from Inquiries & Contacts → My Inquiry API. LumaKol checks every 15 minutes
• Check now on either source fetches at once, up to once every 5 minutes
• If the marketplace turns the details down, the source shows Needs attention with the marketplace’s own message, and the next good check clears it

Pushed sources: one private URL each

Open Connect on the source to copy its URL, then paste it into the service’s webhook setting; Connect shows the exact steps for each service. Every pushed source has its own reader, so the service’s own field names land in the right lead fields without any mapping.

• The URL is private: anyone who has it can send leads to the source. Change URL makes a new one and the old one stops at once
• Google Ads also needs the key shown next to the URL, and Google’s test data is logged as Test without making a lead
• JustDial is switched on by your JustDial account manager, once you send them the URL
• Payments only make a lead when the money comes in: a captured or paid Razorpay payment, an Instamojo payment with the status Credit
• Shopify sends each new customer once, when the customer is created

Forwarded sources: portal lead emails

LumaKol does not log in to property or service portals. You forward the lead emails they already send you to the private address on an email source, and LumaKol reads the name, phone, email and city from each one. Mobile numbers in emails from known Indian portals are saved with +91.

• Gmail: Settings → See all settings → Forwarding and POP/IMAP → Add a forwarding address. Gmail’s confirmation code shows on the LumaKol source within a minute
• Then forward only the portal’s emails: a Gmail filter on the portal’s sender address with Forward it to your LumaKol address
• Outlook: Settings → Mail → Rules → Add new rule, with the portal’s sender as the condition and Forward to as the action

Relayed sources: Zapier, Pabbly Connect and Make

For an app with no source of its own, an automation tool can pass its leads on. Add a Zapier, Pabbly Connect or Make source, copy its URL, and finish the workflow with a step that posts each lead to it: Webhooks by Zapier on Zapier (a paid Zapier plan), Execute API Request in Pabbly Connect, or the HTTP module in Make. Send at least a phone number. Keys called name, phone, email, company, city and notes are picked up on their own; Field names on the source maps any others.

• Facebook and Instagram lead ads come in this way: start the workflow with the Facebook Lead Ads trigger for your Page and form, then post each lead to the source
• Send the record’s own ID as id, so a workflow that runs twice adds the lead once

Decide who gets each source’s leads

Each source has its own routing: one person, shared in turn between the people you tick, or nobody yet so a manager can hand leads out. It also has a starting stage and tags. The person who gets a lead has a push on their phone the moment it lands, and on the Leads page each source’s leads sit in a list named after the source.

Check the first lead arrived

After connecting, send one real enquiry through the service and open the source’s Activity. It lists the latest deliveries, newest first, each as New lead, Repeat, Not added with the reason, or Test. The source itself shows Live, Paused or Needs attention, with its counts and when the last lead came in.

• A number already in your workspace never becomes a second lead: the enquiry is added as a note on the lead you have, and that lead moves up
• The same delivery sent twice is recorded once
• Pause stops a source without losing its settings; Remove stops it for good, and leads it already sent stay in LumaKol