What it is
An online spreadsheet people work on together with nothing to install. In a small business it is often the main record, so automation writes there instead of forcing everyone into a CRM.
How we use it
In lead automation, n8n appends every lead from the Telegram bot as a row in the sheet alongside Bitrix24. The sheet remains a fallback record if the CRM is unavailable.
Where it helps a business
- Part of the team works in a familiar spreadsheet rather than the CRM, and leads should arrive there without copying.
- You need a fallback record in case the CRM is unavailable.
How we use it
In lead automation for a small business the Google Sheets node in n8n appends every lead from the Telegram bot as a row at the end of the tracking sheet, with its status, alongside Bitrix24. Leads accumulate in a familiar format, and the sheet stays a fallback store if the CRM is unavailable. Google access is set in n8n itself, not in the workflow file.
Common problems
- Manual edits break the structure. If someone rearranges the columns, the automation starts writing to the wrong place.
- The sheet keeps growing. After a couple of years thousands of rows slow it down, and it is time to move the records into a CRM or a database.
When you do not need it
If the whole team already works in the CRM and no fallback record is needed, a second copy of leads in a sheet is redundant.