Business Tools · Sales
Leads from a Google Sheet, in your CRM without retyping.
Connect a Google Sheet, match its columns to lead fields, and its rows arrive in CRM as leads — when you ask, or on a schedule.
What it does
Google Sheets, lead fields and the import log
Part of CRM. Connect a sheet once, say which column is which, and choose when it is read. Every run is logged.
Connecting a sheet
- Sign in with Google
- Pick the spreadsheet from your own Google account. The office asks to read it and nothing more.
- Or a key of your own
- For a sheet nobody should sign in for: a service-account key from Google Cloud, with the sheet shared to it.
- The tab and the header row
- Choose which tab is read, and which row holds the column names.
Matching the columns
- Two are required
- Contact person and mobile. A row without them is not taken, and the log says why.
- The rest if you have them
- Title, email, company, address, city, state, country, PIN code, source, status, priority, expected value, description and next action date.
- Columns joined
- First name and surname, say, joined into one field with the separator you choose.
- Tidied on the way in
- Spaces trimmed, phone numbers tidied, text lower-cased, or dates read into your own date format.
- Starting values
- The source new leads get, the status they start at, and a value for any field the sheet has no column for.
When it runs
- Now
- Run it from the sheet’s page whenever you like.
- On a schedule
- Every 15 or 30 minutes; every 1, 2, 3, 6 or 12 hours; once a day or once a week.
- Rows already in
- A row whose mobile is already a lead in that branch is skipped, so running it again doubles nobody.
- A report by email
- After each scheduled run, to an address you give, if you want one.
The import log
- Every run
- When it ran, whether it finished, rows read, leads made, duplicates skipped, errors, and how long it took.
- Every row not taken
- Its row number, the field at fault, the reason, and the row as it was read.
- Downloaded to fix
- The rows not taken download as a CSV, to put right in the sheet.
After every run
The import log: every run counted, every row not taken explained
A schedule runs while nobody watches, so each run leaves a line behind it, and each row it did not take leaves its reason.
Counted, run by run
Each run is one line, with when it ran, whether it finished, and how long it took:
- Rows read — the rows found below the header row
- Imported — the rows that are leads now
- Duplicates — rows whose mobile was already a lead
- Errors — rows the lead would not take
Explained, row by row
Open a run and every row it did not take is listed with its row number in the sheet, the field at fault, the reason, and the row as it was read. Download them as a CSV, put them right in the sheet, and the next run takes them.
Skipped, not doubled
The whole sheet is read each time. A row whose mobile is already a lead in that branch is skipped and counted as a duplicate, so a row already in comes in once.
Hand-offs
From your sheet into CRM, and on to customers
The rows come from whatever fills the sheet, and the leads they become are worked in the parts around CRM.
Whatever fills the sheet
A form, another tool or a colleague typing — anything that writes rows into a Google Sheet can put leads in CRM this way.
CRM →
Each row taken is an ordinary lead there: called, visited, followed up and moved through its statuses like any other.
Customers →
When a lead from the sheet buys, Fetch from Lead carries its name, contact and address onto the customer record.
Lead sync from your own systems →
When the leads come from your own site or software instead of a sheet, it sends them in on a key you issue.
What it costs
The price of lead sync from a sheet
It is part of CRM, which comes in the Sales set with Customers and Forms, priced per person per month. Nothing is added for it.
Sales
₹99.00₹89.10a person, a month
₹267.30 a person for the 3 months, paid at the start.
Paid every three months, the shortest term the set is sold on. Prices exclude GST.
- Sheets connected at once
- The set comes with a limit on how many Google Sheets are connected at a time, raised by asking. It counts sheets, not the rows in them.
- Priced per person
- Each seat is one person who can sign in, and the set is priced on every seat.
- Longer terms cost less a month
- Every term and every add-on is priced on the pricing page.
Before you start
Questions about lead sync from a sheet
The ones asked before a schedule is trusted with the leads, answered as they are — including the ones where the answer is no.
No. A row whose mobile number already belongs to a lead in that branch is skipped and counted as a duplicate in the log, and the lead in CRM is left as it is. Changes to a lead are made on the lead.
No. It only reads: signing in with Google asks for read access and nothing more. Nothing in the sheet is marked, moved or deleted, so it stays exactly as the people filling it left it.
Google Sheets only. An Excel or CSV file can still come into CRM through its own import, which matches on lead code or mobile and lets you skip, overwrite or merge each match.
It is not taken. The log lists it with its row number, the field and the reason, and the rows not taken download as a CSV. Put the row right in the sheet and the next run takes it.
No. Columns fill the lead’s standard fields — contact person, mobile, email, company, address, source, status and the rest listed above. Your own fields are filled on the lead’s page once it is in CRM.
See your own sheet arrive as leads
Bring the sheet your enquiries land in to the demo, and we will connect it with you.