An automated brand monitoring system that scanned Google Shopping daily, verified every listing against a premium tea brand's catalog, and delivered a structured report to Slack before the team's first coffee โ or in this case, tea.
Google Shopping is a competitive battlefield. For a brand like Harney & Sons โ with dozens of SKUs, distinct flavor lines, and a reputation built over decades โ knowing what's showing up when customers search matters.
The team had no systematic way to know what Google Shopping was showing for their brand keywords each morning. Competitors, grey-market sellers, and mislabeled listings could surface and go unnoticed for days.
Harney & Sons carries hundreds of teas across multiple flavor families. Manually searching and verifying each relevant keyword daily wasn't feasible โ the volume was too high and the pattern too repetitive.
When a competitor or unauthorized seller appeared in branded search results, there was no mechanism to catch it quickly. The team needed a red flag, not a weekly report.
A fully automated n8n workflow that runs on a cron schedule every morning โ no manual trigger, no dashboard to check.
At a set time each day, the n8n workflow wakes up and pulls the current list of search terms to monitor. Keywords can be added, removed, or updated by the client without touching the workflow.
n8n ยท cron schedulerEach keyword is run through a Shopping search API, returning the live product listings exactly as a customer would see them โ title, seller, price, and product details.
SerpAPI ยท Google Shopping resultsThe workflow checks each listing: Is this a Harney & Sons product? Is the flavor correct? Is the seller authorized? Results are categorized as confirmed brand listings or flagged anomalies.
n8n logic nodes ยท product catalog matchingA structured message is sent to a dedicated Slack channel. Green attachments confirm brand listings are showing correctly. Red attachments surface the details of anything that needs attention โ seller name, product title, price, and URL.
Slack API ยท n8n Slack nodeThe client doesn't need to log into n8n to change what's being monitored. A reply in the Slack thread with a new keyword or removal command updates the tracked terms directly.
Slack webhook ยท n8n triggerA clean report in the brand's dedicated channel โ green lights for verified listings, red flags with full details when something's off.
Before this system, monitoring Google Shopping was something that happened occasionally โ when someone remembered to check, or when a problem surfaced through a customer complaint. That's a reactive posture for a brand that's worked decades to build recognition.
The shift wasn't just automation โ it was converting a task that required intention and memory into something that happened every single morning without anyone having to think about it. The report shows up in Slack the same way the weather does. The team stopped wondering and started knowing.
The Slack-native update flow was the detail that made it stick. Updating search terms through a thread reply meant the client never had to open a tool they weren't already living in. The workflow adapted to their behavior, not the other way around.
"The best automation is the one the team forgets is running โ because the output just shows up, every morning, without anyone having to ask for it."