Push cleaned Google Sheets leads to a rate-limited CRM with Jitterflow
UnknownUnknown. This template uses community nodes we can't verify statically. Uses community nodes that can't be verified statically (unverified community packages are off by default in 3.0). Static check, last run 2026-10-19.
What this workflow does
This workflow has 12 nodes and runs on a schedule (every hour) (plus 1 other trigger). Along the way it connects Google Sheets and Jitterflow (community).
How it runs
Trigger: On a schedule (every hour) (plus 1 other trigger).
- Read lead sheet (Google Sheets): uses Google Sheets
- List undelivered jobs (Jitterflow): list (dlq)
- Not sent yet (Filter): keeps only the items that match a condition
- Keep sheet leads (Filter): keeps only the items that match a condition
- Clean up lead (Edit Fields (Set)): sets 6 fields: row_number, source, email…
- Mark rejected by the CRM (Google Sheets): update
- Email looks valid? (If): checks a condition and branches into true / false
- Queue lead for the CRM (Jitterflow): send (webhook)
- Mark invalid email (Google Sheets): update
- Mark as queued (Google Sheets): update
Services it uses
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 1 community package, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that n8n-nodes-jitterflow is verified or supports 3.0 (used in Queue lead for the CRM, List undelivered jobs).
Nodes used (6)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Google Sheets
n8n-nodes-base.googleSheets - Filter
n8n-nodes-base.filter - Edit Fields (Set)
n8n-nodes-base.set - If
n8n-nodes-base.if - Jitterflow
n8n-nodes-jitterflow.jitterflow
From the author
Quick overview This workflow runs on two schedules to read new leads from Google Sheets, validate and normalize email addresses, and queue each lead to a rate-limited CRM via Jitterflow, then writes queue status, job IDs, and CRM rejection errors back to the…