This walkthrough was checked in the staging dashboard on September 7, 2026. The screenshots show an empty demonstration setup and contain no service-account address or spreadsheet data.
Before you start
Have the following ready:- An owner or admin account in Nexor.
- A Google Sheet whose first row contains column headers.
- One column with a phone number for every lead. After formatting is removed, a valid value needs at least eight digits.
- The active agent that should receive the imported leads.
Configure an import
1
Open Google Sheets
Go to Integrations → Google Sheets. The management screen remains available even when no automation exists. Select New automation.
2
Choose Import Leads
Keep Type set to Import Leads, then paste the Google Sheets URL. Nexor reads the spreadsheet title, tabs, and header row through its service account.
3
Share the spreadsheet
If the sheet is private, copy the service-account address shown in the dashboard and share the sheet with that address as an Editor. Always use the address displayed for the current environment; do not reuse one from another account or document.
4
Select the tab and agent
Choose one spreadsheet tab and one active agent. The Integrations drawer creates one automation per tab, so repeat the setup for another tab when needed.
5
Map the columns
Map every field explicitly. Nexor does not infer the mapping from header names. Exactly one header must map to Phone.The standard destinations are Phone, Full name, First name, Last name, Email, and City. A custom destination is stored in lead metadata. Full name cannot be combined with First name or Last name, and two headers cannot target the same destination.
6
Create the automation
Review the selected tab, agent, and mapping, then select Create automation. Keep the automation active for the importer to include it in its scheduled checks.
What the import does
- The importer attempts to check active Import automations every five minutes. This is the worker schedule, not a guaranteed delivery time; Google quotas, the worker, and processing time can add delay.
- On the first check, a new automation processes the data rows already present in the tab, starting after the header. It sends them to Nexor in batches of 50.
- After that first check, only rows appended after the processed position are considered. Editing an earlier row does not update its lead. Add new rows at the bottom and avoid inserting, deleting, or reordering rows above the imported range.
- A row without a valid phone number is skipped. Because the processed position still advances, correcting that same row does not automatically retry it; append a corrected row instead.
No product contract for a maximum number of rows, columns, or tabs was found in the current code. This guide therefore does not describe the connection as unlimited.