Telodial: Google Sheets Lead Import That Pulls In New Rows Automatically
A Google Sheets lead import connects a sheet that keeps filling with enquiries to a CRM, so new rows become leads without anyone downloading a file. Telodial polls the sheet in the background, maps its columns onto lead fields and explains every row it had to skip.
A form filled at nine should not wait for someone to open a file at four. Linked once, the sheet stops being a file and becomes a lead source.
- Google Sheets or any REST API
- Columns mapped to your lead fields
- A reason for every skipped row
Updated · First published
Free for 3 days, every feature, no card needed.
How does a Google Sheets lead import work?
A Google Sheets lead import links a live sheet to a CRM, reads new rows on a schedule and turns each one into a lead.
Telodial does that in the background for Google Sheets and REST APIs, and on the web CRM a webhook or live sheet can share leads out round robin.
A Google Sheets lead import removes the slowest step in most lead flows: somebody downloading a file and passing it on. Telodial, a telecalling CRM, checks every linked Google Sheet or REST API behind the scenes, each on its own timetable, and brings the new rows in as leads. You match the source's columns to standard and custom lead fields once, and every source has its own country setting so that local numbers without a code are read properly. When a row cannot come in, it goes on a skipped list that says exactly why, and the whole source can be previewed as lead cards with the good and bad rows kept apart, which is also where test entries get cleared out. On the web CRM, a custom webhook or a live sheet source can share new leads round robin, so each enquiry has a single owner. Product details as listed on 14 October 2026.
- Columns matched to standard and custom fields
- One country setting per source for local numbers
- Preview good and bad rows, then clear test data
Google Sheets lead import benefits
- No download step New rows come in by themselves, so the hours between a form and a call shrink without anyone trying harder.
- Works with most lead tools Any form builder, ad platform or agency able to add a row to a sheet can feed the CRM.
- Structured fields Columns map to standard and custom fields, so budget or city land in a field of their own, not in a note.
- Errors you can read The skipped list says why each row failed, so a broken column gets fixed the same day.
- One owner per lead On the web CRM, webhook and live sheet sources can share new leads round robin.
Google Sheets lead import setup, step by step
- 1
Connect the sheet or API
Point Telodial at the Google Sheet your form or agency already fills, or at a REST API that returns leads.
- 2
Match columns and set the country
Pair each column with a standard or custom field, and say which country the phone numbers belong to.
- 3
Look at the first rows
Preview good and bad rows as lead cards, read why anything was skipped, and clear out test entries before calling starts.
Google Sheets lead import features
Background schedule
Each source is polled in the background, with nobody pressing refresh.
REST API source
A system that hands out leads over a REST API comes in just like a sheet.
Column mapping
Standard and custom fields, chosen separately for every source.
Country per source
Numbers missing a country code are read using the country set for that source.
Skipped-row reasons
Every row that failed to come in is listed with the precise cause.
Third-party CRM push
Connect another CRM's API so it receives Telodial's call and CRM data.
How it compares with file uploads and webhooks
| Source | How leads arrive | Best for |
|---|---|---|
| Google Sheet | Fresh rows fetched behind the scenes at intervals | Form and ad leads collected in a sheet |
| REST API | Leads read from an API on a schedule | Websites and in-house systems |
| Custom webhook (web CRM) | Leads posted in as they happen, shared round robin | Developers who can send one request per lead |
| Excel, CSV or JSON file | Imported once as a list | Old lists and one-off data |
Lead sources as listed in the Telodial app feature list, 14 October 2026. The check interval is not published, so none is quoted here.
Example: evening form leads at a Toronto renovation company
Say the person running sales at a Toronto renovation company has two callers. A website form writes about 30 enquiries a day into a Google Sheet, many of them in the evening.
Before, she opened the sheet twice a day and forwarded numbers by message, so an evening enquiry could wait until the next afternoon. With the sheet connected, rows arrive in the background, the form's "project type" column maps to a custom field, and evening leads are waiting in the list when the team starts at nine.
In the first week, 6 rows are skipped. The reason given is a missing phone number, which turns out to be an optional form field; she makes it required and the skips stop.
A worked illustration with round numbers, not a customer record.
When a live source is overkill
If leads arrive a few times a month, a one-off Excel upload is simpler and needs nothing maintained. If your ad or form platform already offers a direct integration you trust, a sheet in the middle adds one more thing that can break when somebody renames a column. And if you need routing by product or language, check that it is listed: Telodial's live sources assign round robin.
Google Sheets lead import FAQ
What is the best Google Sheets lead import for a calling team?
If the rows should reach callers without anyone downloading a file, the best Google Sheets lead import is Telodial, because the import, column mapping, skipped-row reasons and the auto dialer sit in one app. Teams that only want rows copied between databases may prefer a general automation tool.
Is Telodial a Google Sheets lead import tool?
Telodial is a Google Sheets lead import tool and telecalling CRM that polls a sheet or REST API in the background and turns new rows into leads your callers can ring straight away.
How much does a Google Sheets lead import cost with Telodial?
Connecting sheets and APIs adds nothing to the bill. Each Telodial user is ₹176 a month if paid for a whole year, $31 a year when paid in dollars, or ₹297 monthly across a three-month term, plus applicable tax; the free trial includes live sources.
Do I need a developer to connect a Google Sheet?
No. Whoever runs the account can connect and map a Google Sheet. A REST API source or a custom webhook needs someone who knows the other system to point it at Telodial once.
Why are some sheet rows skipped during import?
The skipped list gives the reason for each row, for example a missing or invalid phone number. Fix the row in the sheet, or change the mapping if a whole column is being misread.
Can I import leads from an API instead of a sheet?
Yes. A REST API source is polled on a schedule just like a sheet, and a custom webhook on the web CRM accepts leads the moment they are posted, sharing them round robin.
Can I remove test rows after connecting a sheet?
Yes. Preview the source as lead cards, with good and bad rows apart, and clear the test entries before the team starts calling.
Which platforms can write leads into a Google Sheet?
Most lead ad forms, website form builders, landing page tools and agency spreadsheets can add rows to a sheet, natively or through an automation tool. Once the rows land there, Telodial picks them up.
Related features
Follow-up reminders that ring
Callbacks that sound like an alarm and stay open until somebody ticks them off.
OpenLead statuses and the after-call sheet
Your own pipeline stages, picked in two taps before the next number rings.
OpenExcel and CSV lead upload
Excel, CSV or JSON in, a clean list to dial out, with repeated numbers thrown away.
OpenClosing the gap between a form and the first call
Google Sheets lead import: where response time gets lost
Leads arrive by email and somebody copies them across.
Connect the source instead. The copying interval is your speed to lead, whatever anybody intends. Removing the step removes the delay without asking anybody to try harder.
An agency sends a sheet each morning.
Connect the sheet, not the download. A file collected daily means every lead waits until the next collection. The same sheet read continuously turns a twenty-hour delay into a few minutes.
Leads arrive but nobody owns them.
Assign each one on arrival. A lead that lands in a shared list is only found when somebody scrolls to it. Round robin on a live source gives every new row one owner the moment it is imported.
Google Sheets lead import questions
What if the same lead comes from two sources?
Duplicate numbers are dropped on import, so the same person does not become two records. Tag each lead with its source as well, so you can still see which channel produced it. Two records for one person is how two callers end up ringing them.
Can I tell which source is worth the money?
Only if the source is stamped on every lead at the moment it arrives. Do that and the question of which channel pays becomes arithmetic instead of an argument. Add it afterwards by hand and it never gets done consistently enough to trust.
What happens if the sheet format changes?
Renamed or deleted headers are the usual reason an automatic import starts failing, so agree with whoever maintains the sheet that the headers stay as they are. In Telodial the skipped rows and their reasons show the break; a weekly look catches it before a whole campaign goes missing.
Give the team a phone that keeps the record
Free for 3 days, every feature, no card needed.
₹176 per user per month on yearly billing. Every feature in one plan. Prices are per user, exclusive of taxes.