Google Sheets + WhatsApp tracking updates, sent smart
Your team shouldn’t be answering “Any update?” all day. But once shipments leave the warehouse, customers get anxious, statuses change quietly, and you end up copy-pasting tracking info from courier sites into messages that nobody enjoys sending.
This is where Sheets WhatsApp tracking helps fast. Support leads feel it when the inbox piles up. Store owners feel it when repeat buyers hesitate. And ops teams get stuck doing the same checks every morning.
This workflow pulls your shipment list from Google Sheets, checks Delhivery and DHL automatically, updates your sheet, then notifies customers by WhatsApp and email only when something actually changes. You’ll see how it works, what you need, and where teams usually trip up.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Google Sheets + WhatsApp tracking updates, sent smart
flowchart LR
subgraph sg0["Flow 1"]
direction LR
n0@{ icon: "mdi:cog", form: "rounded", label: "Daily Trigger", pos: "b", h: 48 }
n1@{ icon: "mdi:database", form: "rounded", label: "Get Shipments List", pos: "b", h: 48 }
n2@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Filter Active Shipments", pos: "b", h: 48 }
n3["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Track via Delhivery"]
n4["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Track via DHL"]
n5@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Route by Courier", pos: "b", h: 48 }
n6["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Parse Tracking Data"]
n7@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Check Status Change", pos: "b", h: 48 }
n8@{ icon: "mdi:database", form: "rounded", label: "Update Google Sheet", pos: "b", h: 48 }
n9["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Send WhatsApp Update"]
n10@{ icon: "mdi:message-outline", form: "rounded", label: "Send Email Update", pos: "b", h: 48 }
n11["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Execution Summary"]
n0 --> n1
n4 --> n6
n5 --> n3
n5 --> n4
n10 --> n11
n1 --> n2
n7 --> n8
n7 --> n9
n7 --> n10
n6 --> n7
n3 --> n6
n8 --> n11
n9 --> n11
n2 --> n5
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n2,n5,n7 decision
class n1,n8 database
class n3,n4,n9 api
class n6,n11 code
classDef customIcon fill:none,stroke:none
class n3,n4,n6,n9,n11 customIcon
The Problem: Tracking Updates Turn Into Daily Firefighting
Shipment tracking looks simple until you do it at scale. One spreadsheet row becomes ten courier page refreshes, then a WhatsApp message, then an email “just in case.” Multiply that by a few dozen active orders and you’ve lost your morning to tabs, logins, and status codes that don’t match across couriers. Worse, you often notify customers when nothing meaningful changed, so they reply with more questions. It’s noisy, and honestly it trains customers to expect manual updates from you.
The friction compounds. Here’s where it usually breaks down in real life.
- Someone checks Delhivery and DHL one-by-one, which eats about 1–2 hours on a normal day.
- Status names differ across couriers, so “in transit” and “on the way” get recorded inconsistently in your sheet.
- Customers get duplicate messages when you send updates on a schedule instead of on real changes.
- Delivered orders keep getting rechecked because nobody reliably filters them out.
The Solution: Daily Tracking Checks With Change-Only Alerts
This n8n workflow runs every day at 9 AM and acts like a quiet tracking assistant. It starts by pulling your shipment roster from Google Sheets, then ignores anything already delivered or missing a tracking number. Next, it routes each shipment to the right courier (Delhivery or DHL) and makes real-time tracking requests using your API credentials. After that, it normalizes the response into a consistent set of fields (status, location, estimated delivery, and last updated) and compares the new status to what’s already stored in the sheet. Only when there’s a real status change does it update the row, send a WhatsApp notification, and email the customer. Finally, it logs an execution summary so you can see what happened that run.
The workflow begins with a scheduled trigger, then moves through “fetch, filter, route, check.” Once it detects a status shift, it updates Google Sheets and sends WhatsApp plus email in the same pass. No changes? No messages. That’s the whole point.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you have 40 active shipments in a Google Sheet and you check updates every morning. Manually, even a quick routine is maybe 2 minutes per tracking number once you include opening the courier page, finding the right row, and sending a message, so that’s about 80 minutes a day. With this workflow, you spend about 10 minutes maintaining the sheet (new orders in, delivered orders out), then the 9 AM run does the rest and only messages customers when something changed. Most days, that means you get an hour back before lunch.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Google Sheets to store the shipment roster.
- WhatsApp Business API to send customer notifications.
- Delhivery + DHL API keys (get them from your Delhivery/DHL developer or account portal).
Skill level: Intermediate. You’ll connect accounts, paste API keys, and confirm your sheet columns match the workflow.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A 9 AM schedule kicks it off. The Cron trigger runs daily, so you get a predictable update cycle without someone remembering to “do tracking.”
Your shipment roster comes from Google Sheets. The workflow reads a sheet with columns like tracking_number, order_id, customer_email, customer_phone, courier, status, location, last_updated, and estimated_delivery. If you already maintain a fulfillment sheet, this becomes your single source of truth.
Courier checks happen automatically. It filters out delivered items and empty tracking numbers, then routes each row to the right API call (Delhivery or DHL). Responses are normalized so you’re not juggling two different formats.
Updates only fire when something changed. The workflow compares the new status to what’s currently in your sheet. When there’s a status shift, it updates the row, sends a WhatsApp message, sends an email, and logs a run summary.
You can easily modify the courier routing to add another provider based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Scheduled Trigger
Set the workflow to run on a schedule so it can periodically check shipment statuses.
- Add and open Scheduled Automation Trigger to define when the workflow runs.
- Configure the schedule settings you want (daily, hourly, or custom cron) in Scheduled Automation Trigger.
- Leave Flowpast Branding as a non-functional note for documentation and attribution.
Step 2: Connect Google Sheets
Pull shipment data from your spreadsheet and keep it updated after status changes.
- Open Retrieve Shipment Roster and set Document to
jko9876trde456yhnand Sheet to=iuhgt678io. - Credential Required: Connect your googleApi credentials in Retrieve Shipment Roster.
- Open Modify Sheet Records and set Operation to
update, Document to0iuhgy678o, and Sheet to=09iuok. - Credential Required: Connect your googleApi credentials in Modify Sheet Records.
⚠️ Common Pitfall: Make sure the sheet columns match the fields produced by Normalize Tracking Details (e.g., tracking_number, current_status, last_updated), or updates may fail.
Step 3: Filter and Route Shipments by Courier
Only process active shipments and route them to the correct carrier API.
- In Filter Ongoing Shipments, confirm the conditions: status
notEqualsdeliveredand tracking_numbernotEmptywith={{ $json.tracking_number }}. - In Courier Branch Logic, keep the condition courier equals
delhiveryusing={{ $json.courier }}. - Verify the routing: Filter Ongoing Shipments → Courier Branch Logic which splits to Delhivery API Request and DHL API Request.
Step 4: Configure Carrier API Calls and Normalize Results
Call the carrier tracking endpoints and normalize response data into a consistent schema.
- In Delhivery API Request, set URL to
https://track.delhivery.com/api/v1/packages/json/and the query parameter waybill to={{ $json.tracking_number }}. - Credential Required: Connect your httpHeaderAuth credentials in Delhivery API Request.
- In DHL API Request, set URL to
https://api-eu.dhl.com/track/shipmentsand the query parameter trackingNumber to={{ $json.tracking_number }}. - Credential Required: Connect your httpHeaderAuth credentials in DHL API Request.
- In Normalize Tracking Details, keep the provided JavaScript to map carrier responses into standardized fields (e.g.,
current_status,location,last_updated). - Confirm Normalize Tracking Details outputs to Validate Status Shift for change detection.
⚠️ Common Pitfall: If the carrier API response structure changes, update the parsing logic in Normalize Tracking Details or statuses may default to in_transit.
Step 5: Configure Updates and Notifications
When a status changes, update the sheet and notify customers via WhatsApp and email.
- In Validate Status Shift, keep the boolean filter
={{ $json.status_changed }}equalstrue. - Note the parallel execution: Validate Status Shift outputs to both Modify Sheet Records and Dispatch WhatsApp Alert and Email Update Notice in parallel.
- In Dispatch WhatsApp Alert, set URL to
https://api.whatsapp.com/sendand confirm phone uses={{ $json.customer_phone }}and the message text template includes{{ $json.order_id }},{{ $json.tracking_number }}, and{{ $json.current_status }}. - In Email Update Notice, set Subject to
Shipment Update - Order #{{ $json.order_id }}, To Email to={{ $json.customer_email }}, and From Email to[YOUR_EMAIL]. - Credential Required: Connect your smtp credentials in Email Update Notice.
- Keep Run Summary Log connected from Modify Sheet Records, Dispatch WhatsApp Alert, and Email Update Notice to log execution summary data.
⚠️ Common Pitfall: Dispatch WhatsApp Alert has no credentials configured—ensure your API endpoint accepts unauthenticated requests or add authentication to avoid failed notifications.
Step 6: Test and Activate Your Workflow
Run a manual test to confirm API calls, updates, and notifications before turning on automation.
- Click Execute Workflow and verify Retrieve Shipment Roster returns rows with
tracking_numberandstatus. - Confirm either Delhivery API Request or DHL API Request runs based on Courier Branch Logic, and that Normalize Tracking Details outputs
current_statusandstatus_changed. - Check that Modify Sheet Records updates the sheet, and that Dispatch WhatsApp Alert and Email Update Notice send notifications for changed statuses.
- Open the execution log in Run Summary Log and confirm summary counts for processed and updated shipments.
- When the test looks correct, switch the workflow to Active to enable scheduled automation.
Common Gotchas
- Google Sheets credentials can expire or need specific permissions. If things break, check the Google connection inside n8n credentials and confirm the sheet is shared with the connected Google account.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.
Frequently Asked Questions
About 30–60 minutes if your APIs are ready.
No. You’ll mostly connect accounts and paste API keys. The only “technical” part is making sure your Google Sheet columns match the workflow.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in courier/WhatsApp API costs, which depend on how many shipments you check and how many messages you send.
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, but make sure your courier APIs can handle the volume. Change the Cron schedule from daily to hourly (for example, “0 * * * *”), then keep the “status change” filter exactly as-is so customers don’t get spammed. Common customizations include adding a quiet window at night, changing WhatsApp wording by courier, and skipping notifications after the first delivery attempt.
Most of the time it’s an expired OAuth connection or the sheet isn’t shared with the same Google account used in n8n. Reconnect the Google Sheets credential in n8n, then verify the sheet ID is correct and the tab name matches what the node expects. If the workflow suddenly can’t “find columns,” your header row probably changed (extra spaces and renamed columns cause this). Also check execution logs for a permissions error, because it usually tells you exactly what Google blocked.
On n8n Cloud Starter, you can usually handle a few thousand runs a month, which is plenty for many small shops checking daily. If you self-host, there’s no execution cap, so your limit becomes courier rate limits and your server size. Practically, teams often run this against 50–200 active shipments per day without thinking about it, as long as API quotas are configured correctly.
Often, yes. This workflow needs filtering, branching by courier, and “only send when status changes,” and n8n handles that logic cleanly without turning it into a pricey multi-step zap. You also get self-hosting, which matters when you don’t want per-task limits. Zapier or Make can still be fine if you’re only tracking a handful of shipments and you want the quickest possible setup. If you’re unsure, Talk to an automation expert and you’ll get a straight answer based on your volume and tools.
Once this is running, customers get timely updates without you babysitting courier pages. You’ll still care about delivery, of course. You just won’t spend your day proving it.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
