Block 1 - Run Enrichment
- Type / Role
- n8n-nodes-base.manualTrigger - manualTrigger
- Config choices
- Version 1
How it works • Reads all rows from a Google Sheet • Splits them into configurable batches (default: 5 rows per batch) • Calls any external REST API once per row (GET or POST, Header Auth) • Waits 1...
n8n-nodes-base.manualtrigger, n8n-nodes-base.stickynote, n8n-nodes-base.googlesheets, n8n-nodes-base.splitinbatches, n8n-nodes-base.httprequest, n8n-nodes-base.wait, n8n-nodes-base.if, n8n-nodes-base.set
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Patrick Siewert.
Original n8n.io source• Reads all rows from a Google Sheet • Splits them into configurable batches (default: 5 rows per batch) • Calls any external REST API once per row (GET or POST, Header Auth) • Waits 1 second between batches to stay within API rate limits • Routes responses: writes enriched data back to the sheet on success, logs errors on failure • Loops through all batches until the full sheet is processed • Want more REST API workflows? See n8n webhook & API templates ranked by demand
• Takes ~10 minutes to configure • Connect your Google Sheets OAuth2 credential to both Sheet nodes • Set your Sheet ID and tab name in the Read Rows node • Paste your API endpoint URL in the Call API node and connect your Header Auth credential • Adjust batch size and wait duration via the sticky notes inside the workflow • Update the Update Row node with the column(s) you want to write back
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 | Enrich Google Sheets rows via any REST API in rate-limited batches |
|---|---|
| Complexity | intermediate |
| Nodes | 12 |
| Categories | Lead Generation |
| Author | Patrick Siewert |
| Published | 20 Mar 2026 |
Use the JSON export at /data/workflows/14205/14205.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.
How it works • Reads all rows from a Google Sheet • Splits them into configurable batches (default: 5 rows per batch) • Calls any external REST API once per row (GET or POST, Header Auth) • Waits 1...
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 Lead Generation use case.