Google Sheets + Telegram alerts for Amazon price drops
Checking Amazon prices by hand sounds simple. Then you’re doing it for 30 SKUs, across a messy spreadsheet, while someone Slacks you “did we miss the drop?” and you realize you’re basically running a tiny monitoring desk.
This Amazon price alerts automation hits e-commerce operators hardest, but pricing analysts and retail founders feel it too. You get consistent monitoring from a Google Sheets list and fast Telegram alerts when changes actually matter.
Below you’ll see how the workflow runs in n8n, what results to expect, and what you need to turn your sheet into a reliable price-watch system.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Google Sheets + Telegram alerts for Amazon price drops
flowchart LR
subgraph sg0["Scheduled Automation Start Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "Scheduled Automation Start", pos: "b", h: 48 }
n1@{ icon: "mdi:database", form: "rounded", label: "Retrieve Sheet Rows", pos: "b", h: 48 }
n2@{ icon: "mdi:swap-vertical", form: "rounded", label: "Batch Iterate Items", pos: "b", h: 48 }
n3@{ icon: "mdi:cog", form: "rounded", label: "Decodo Amazon Fetch", pos: "b", h: 48 }
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/code.svg' width='40' height='40' /></div><br/>Compute Price Delta"]
n5@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Route by Price Shift", 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/telegram.svg' width='40' height='40' /></div><br/>Alert Leadership via Telegram"]
n7@{ icon: "mdi:location-exit", form: "rounded", label: "Schedule Review Meeting", pos: "b", h: 48 }
n8@{ icon: "mdi:cog", form: "rounded", label: "No-Action Placeholder", pos: "b", h: 48 }
n9@{ icon: "mdi:message-outline", form: "rounded", label: "Email Stakeholder Update", pos: "b", h: 48 }
n10@{ icon: "mdi:cog", form: "rounded", label: "Pause Execution", pos: "b", h: 48 }
n10 --> n2
n3 --> n4
n7 --> n10
n5 --> n6
n5 --> n8
n5 --> n9
n2 --> n3
n0 --> n1
n9 --> n10
n1 --> n2
n4 --> n5
n8 --> n10
n6 --> n7
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 n0 trigger
class n5 decision
class n1 database
class n4 code
classDef customIcon fill:none,stroke:none
class n4,n6 customIcon
The Problem: Price Drops Don’t Wait for Your Spreadsheet
Most teams start with “we’ll just check prices once a day.” Then the catalog grows. A few SKUs become 50. Someone adds new URLs, somebody else changes the baseline, and suddenly you’re copying prices into cells, trying to remember what “normal” looked like last week. It’s not just time. It’s the mental load of constantly wondering if today’s change is real, temporary, or something you should act on immediately. And if you miss a meaningful drop, you lose the window to react.
It adds up fast. Here’s where it breaks down in real life.
- Manually opening Amazon listings for every row in your Google Sheet can eat about 2 hours on a normal monitoring day.
- People notice only the obvious drops, while smaller but important shifts slip by because no one has time to compare against a baseline properly.
- Alerts are inconsistent because they rely on someone remembering to message the team, which means action happens late or not at all.
- When you do catch a spike, coordinating a quick review turns into a back-and-forth instead of a scheduled decision moment.
The Solution: Scheduled Monitoring + Smart Routing for Alerts
This workflow turns a simple Google Sheets list of Amazon URLs into a scheduled price monitoring system that knows when to stay quiet and when to escalate. It starts on a timer, pulls your rows (URL plus baseline price), and processes them in controlled batches so you don’t hammer your data source or hit rate limits. For each product, it uses Decodo to fetch real-time Amazon details like the current price and title, then calculates the price delta against your baseline. Based on that change, n8n routes the item down the right path: leadership gets a Telegram alert for high increases, meaningful drops trigger a rich HTML email to stakeholders, and “normal” changes log no noise. When escalation happens, it can also create a Google Calendar meeting automatically so the team reviews quickly instead of arguing in chat.
The workflow begins with a scheduled run and a sheet lookup. Decodo collects the live product data, then a small calculation determines the price shift. Finally, a routing step decides: Telegram + Calendar, email, or no action, then the workflow waits and continues until every row has been checked.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you track 40 Amazon URLs in a Google Sheet. Manually, even a “quick check” is maybe 3 minutes per item once you open the page, find the right price, and compare to your baseline, which is about 2 hours. With this workflow, you spend about 5 minutes updating the sheet when you add products, then the scheduled run fetches prices in batches and sends Telegram or email only when thresholds are crossed. You stop babysitting the list.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Google Sheets for your URL + baseline list.
- Decodo to fetch Amazon product data reliably.
- Telegram to alert leadership fast when escalations happen.
- Gmail to email stakeholders when prices drop.
- Google Calendar to auto-schedule review meetings on spikes.
- Decodo API credentials (get them from your Decodo dashboard).
Skill level: Intermediate. You’ll connect accounts, map a few fields from your sheet, and adjust alert thresholds confidently.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A scheduled run kicks things off. n8n starts this automation at the interval you choose, so monitoring happens even when nobody is thinking about it.
Your spreadsheet becomes the source of truth. The workflow pulls rows from Google Sheets (or Microsoft Excel 365 if you adapt it), reading the Amazon URL and the baseline price you want to compare against.
Live Amazon data is fetched and compared. Each item is processed in batches, Decodo fetches current product details, and a calculation determines how far the current price moved from your baseline. If you’re using an AI Agent or OpenAI Chat Model nodes in your version, this is also where you can generate a cleaner summary line for emails or Telegram alerts.
Routing decides who hears about it. A “high / normal / low” decision sends Telegram alerts for high increases (and schedules a Google Calendar meeting), sends a formatted Gmail update for drops, or does nothing when movement is normal.
You can easily modify alert thresholds to match your margin targets based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Schedule Trigger
This workflow starts on a scheduled interval and kicks off the pricing check cycle.
- Add and open Scheduled Automation Start.
- Set the schedule rule in Scheduled Automation Start to match your desired interval (the node uses the default rule → interval structure).
- Confirm the execution flow begins with Scheduled Automation Start → Retrieve Sheet Rows.
Step 2: Connect Google Sheets
This step loads your product URLs and baseline prices from a sheet.
- Open Retrieve Sheet Rows and select your spreadsheet in Document.
- Set Sheet Name to
list urls(valuegid=0). - Credential Required: Connect your googleSheetsOAuth2Api credentials.
- Ensure your sheet includes columns like url and baseline price (usd) used later in calculations.
Tip: Keep the url field populated for every row, as Decodo Amazon Fetch reads it directly with {{ $json.url }}.
Step 3: Batch and Fetch Live Prices
Items are processed in batches, and each URL is scraped for live pricing data.
- Open Batch Iterate Items and keep default settings for batch processing.
- Connect Retrieve Sheet Rows → Batch Iterate Items → Decodo Amazon Fetch.
- In Decodo Amazon Fetch, set Operation to
amazon. - Set URL to
{{ $json.url }}. - Credential Required: Connect your decodoApi credentials.
⚠️ Common Pitfall: If the sheet rows do not include a valid url field, Decodo Amazon Fetch will fail to return pricing data.
Step 4: Compute Price Changes and Route by Threshold
This step calculates the price delta and routes results to alerts or updates.
- Open Compute Price Delta and confirm the JavaScript calculates
diffanddiffPercentageusing Batch Iterate Items data. - Ensure Compute Price Delta references
$('Batch Iterate Items').first().json['baseline price (usd)']. - Open Route by Price Shift and verify three rules:
- High:
{{ $json.diffPercentage }}>10 - Normal:
{{ $json.diffPercentage }}≥0 - Low:
{{ $json.diffPercentage }}<0 - Confirm Compute Price Delta → Route by Price Shift connection.
Step 5: Configure Alerts, Meetings, and Updates
Based on the route, alerts are sent, meetings are scheduled, or updates are emailed.
- For the High path, open Alert Leadership via Telegram and keep the message template using expressions like
{{ $json.title }}and{{ $json.diffPercentage }}. - Credential Required: Connect your telegramApi credentials.
- Open Schedule Review Meeting and set Start to
{{ $now.plus(2, 'hour') }}and End to{{ $now.plus(3, 'hour') }}. - Set Summary to
[IMPORTANT DISCUSSION] Price Increase {{ $('Compute Price Delta').item.json.title }}and update Attendees with your emails. - Credential Required: Connect your googleCalendarOAuth2Api credentials.
- For the Low path, open Email Stakeholder Update and set Send To to
[YOUR_EMAIL]. - Keep Subject as
Price Drop - {{ $('Compute Price Delta').item.json.title }}and the HTML Message template intact. - Credential Required: Connect your gmailOAuth2 credentials.
- For the Normal path, No-Action Placeholder intentionally performs no action.
Route by Price Shift outputs to Alert Leadership via Telegram, No-Action Placeholder, or Email Stakeholder Update based on the rule matched.
Step 6: Manage the Pause and Batch Loop
After each action branch, the workflow pauses and then continues batch processing.
- Confirm Alert Leadership via Telegram → Schedule Review Meeting → Pause Execution.
- Confirm Email Stakeholder Update → Pause Execution and No-Action Placeholder → Pause Execution.
- Verify Pause Execution outputs back to Batch Iterate Items to continue processing remaining items.
Tip: Use Pause Execution to prevent API rate limits when checking many products.
Step 7: Test and Activate Your Workflow
Validate the full flow before turning on scheduled automation.
- Click Execute Workflow to run a manual test from Scheduled Automation Start.
- Confirm Retrieve Sheet Rows pulls data and Decodo Amazon Fetch returns live price results.
- Check that Compute Price Delta outputs
price,baseline, anddiffPercentagevalues. - Verify the correct path is taken in Route by Price Shift and the corresponding alert or email is sent.
- Once successful, toggle the workflow to Active for production scheduling.
Common Gotchas
- Google Sheets credentials can expire or need specific permissions. If things break, check the n8n Credentials tab and your Google account’s connected app access first.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Decodo limits and Amazon responses change. If fetches start failing, review your Decodo usage logs and consider lowering batch size so requests are less bursty.
Frequently Asked Questions
About 30–60 minutes if your accounts and sheet are ready.
No. You’ll mainly connect accounts, map fields from your sheet, and set your thresholds.
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 Decodo API costs based on your request volume.
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, and honestly it’s the first thing you should tune. Adjust the threshold logic in the Compute Price Delta step (where the difference is calculated) and the routing rules in Route by Price Shift. Common customizations include separate thresholds by brand, different actions for weekends, and adding extra channels like Slack or WhatsApp alongside Telegram and email.
Most of the time it’s an API key issue or a plan limit. Regenerate your Decodo API credentials, update them in n8n, and check your Decodo dashboard logs for blocked or rate-limited requests. Also make sure your batch size isn’t too aggressive, because bursts can trigger temporary failures.
A few hundred SKUs per run is realistic for most small teams, and you can scale further by lowering batch size and increasing the schedule frequency.
Sometimes. This workflow relies on batch processing, routing logic, and a “wait and continue” loop, which n8n handles cleanly without turning every branch into another paid task. Zapier or Make can still work if your setup is tiny, but costs usually climb once you monitor lots of rows and send multi-channel alerts. Another factor is control: self-hosted n8n gives you more room to run frequent checks without worrying about per-task pricing. If you want help choosing, Talk to an automation expert.
Once this is running, price monitoring stops being a daily chore and becomes a background system. The workflow handles the repetitive checks. You focus on the decisions.
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.