Block 1 - Google Sheets Trigger
- Type / Role
- n8n-nodes-base.googleSheetsTrigger - googleSheetsTrigger
- Config choices
- Version 1
This workflow is provided as-is. Please review and test before using in production.
Before Using this Template first search LEDGERS in the nodes list and Update! The workflow automates contact creation in LEDGERS from a Google Sheets document, while performing validation checks on...
n8n-nodes-base.googlesheetstrigger, n8n-nodes-base.splitinbatches, n8n-nodes-base.noop, @ledgers/n8n-nodes-ledgers-cloud.ledgers, n8n-nodes-base.gmail, n8n-nodes-base.if, n8n-nodes-base.code, n8n-nodes-base.googlesheets
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by LEDGERS.
Original n8n.io sourceBefore Using this Template first search LEDGERS in the nodes list and Update!
The workflow automates contact creation in LEDGERS from a Google Sheets document, while performing validation checks on contact data to ensure data quality.
Key Features: ✅ Google Sheets Trigger – Polls the sheet every minute to detect new or updated rows. ✅ Contact Name Validation – Checks if the contact name is provided; sends an email notification if missing. ✅ Email & Mobile Validation – Uses custom code to validate the format of email and mobile fields. ✅ Dynamic Routing –
If both email and mobile are valid → proceeds to create the contact in LEDGERS.
If either is invalid → sends an error notification via Gmail. ✅ Mobile Number Formatter – Extracts country code and mobile number for consistent formatting before creating the contact. ✅ LEDGERS API Integration – Creates the contact using the LEDGERS custom node. ✅ Error Handling – If contact creation fails (e.g., duplicate email), sends a failure email with details. ✅ Audit Trail – Appends results (including timestamps) back to Google Sheets for record-keeping.
Extended Field Support This workflow is designed to be flexible. 👉 Along with core fields (Name, Email, Mobile), users can optionally map and include additional fields when creating a contact in LEDGERS, such as:
➡ The workflow’s LEDGERS node can be configured to map these fields dynamically from Google Sheets if desired.
Customization ✅ Users can extend or modify the workflow to handle these additional fields without needing structural changes — just by updating the mapping in the LEDGERS node parameters.
Requirements: A connected Google Sheets document with at least Name column
Configured Gmail credentials for sending email notifications
A LEDGERS account with API access and credentials set up in n8n
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Validate and create LEDGERS contacts from Google Sheets with error handling |
|---|---|
| Complexity | intermediate |
| Nodes | 14 |
| Categories | CRM |
| Author | LEDGERS |
| Published | 16 Jun 2025 |
Use the JSON export at /data/workflows/4961/4961.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
Before Using this Template first search LEDGERS in the nodes list and Update! The workflow automates contact creation in LEDGERS from a Google Sheets document, while performing validation checks on...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your CRM use case.