Decodo + Slack: Amazon book reports ready to share
You pull “top books” from Amazon, then it starts. Copy links into a doc. Clean up titles. Fix prices that got pasted wrong. By the time it’s shareable, you’ve already burned the morning.
Marketing leads feel this when they need a weekly “picks” roundup. A small business owner feels it when buying inventory or gifts in bulk. And analysts get stuck polishing spreadsheets instead of making decisions. This Decodo Slack reports automation turns a messy Amazon page into a ready-to-share Google Doc and PDF, delivered straight to Slack.
You’ll see what the workflow does, what you need to connect, and how to adapt it for your own reporting cadence.
How This Automation Works
Here’s the complete workflow you’ll be setting up:
n8n Workflow Template: Decodo + Slack: Amazon book reports ready to share
flowchart LR
subgraph sg0["When clicking ‘Execute workflow’ Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "When clicking ‘Execute workf..", pos: "b", h: 48 }
n1@{ icon: "mdi:brain", form: "rounded", label: "OpenAI Chat Model", pos: "b", h: 48 }
n2@{ icon: "mdi:robot", form: "rounded", label: "Structured Output Parser", 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/>Create document file"]
n4@{ icon: "mdi:cog", form: "rounded", label: "Convert document to PDF", pos: "b", h: 48 }
n5@{ icon: "mdi:swap-vertical", form: "rounded", label: "Configure Google Drive Folder ", pos: "b", h: 48 }
n6@{ icon: "mdi:robot", form: "rounded", label: "Product Analyzer Agent", pos: "b", h: 48 }
n7@{ icon: "mdi:swap-vertical", form: "rounded", label: "Edit Fields", pos: "b", h: 48 }
n8["<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/>HTML Response Parser"]
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/slack.svg' width='40' height='40' /></div><br/>Upload report to Slack "]
n10["<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/>Build 📚 Book Purchase Report"]
n11@{ icon: "mdi:cog", form: "rounded", label: "Decodo", pos: "b", h: 48 }
n11 --> n8
n7 --> n11
n1 -.-> n6
n3 --> n4
n8 --> n6
n6 --> n10
n4 --> n9
n2 -.-> n6
n5 --> n3
n10 --> n5
n0 --> 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 n2,n6 ai
class n1 aiModel
class n3 api
class n8,n10 code
classDef customIcon fill:none,stroke:none
class n3,n8,n9,n10 customIcon
Why This Matters: Shareable Amazon book reports take too long
Amazon pages are great for browsing, not for reporting. The moment someone asks, “Can you summarize the top 30 books and send it to the channel?” you’re stuck doing busywork that feels small but drags on: extracting titles, authors, prices, ratings, then reformatting it so it doesn’t look like a pasted mess. And if the page is dynamic (which it often is), a quick copy-paste misses chunks of content, duplicates items, or grabs weird text. Worse, once you’ve shared it, it’s already stale. Next week you do it again.
The friction compounds. Here’s where it breaks down.
- Building a clean list from an Amazon category page can take about an hour, and that’s before you write an executive summary.
- Small formatting mistakes sneak in, which means stakeholders question the data even when the picks are solid.
- Different people pull the “same” list and get different results because the page loads differently by device, location, or timing.
- By the time the report is a Doc and a PDF, the window to act (buy, promote, brief a team) is already closing.
What You’ll Build: Amazon page → Book report → Slack delivery
This workflow starts with a simple manual run in n8n, where you paste an Amazon URL (a category page, a search results page, or a curated list) and choose a device type like desktop or mobile. n8n sends that URL to the Decodo Scraper API, which loads the page with headless browsing so JavaScript-heavy content actually shows up. Once the HTML comes back, the workflow cleans it up, then an AI agent extracts structured “book” objects like title, author, rating, price, and link. From there, the workflow composes a purchase-ready report with a summary and a table, creates a Google Doc in a chosen Drive folder, exports it as a PDF, and posts the PDF (plus the Doc link) to Slack for instant sharing.
The workflow kicks off from n8n with your URL and a few optional inputs. Decodo handles the hard part of consistently fetching the page content. OpenAI then turns messy markup into a strict JSON list, and the workflow packages it into Docs + PDF so Slack gets something polished, not raw data.
What You’re Building
| What Gets Automated | What You’ll Achieve |
|---|---|
|
|
Expected Results
Say you publish a weekly “Top 25 books to consider” update for your team. Manually, it’s maybe 2 minutes per book to copy the title, author, rating, price, and link into a doc, plus another 20 minutes to clean formatting and add a short summary. That’s about 70 minutes each run. With this workflow, you paste the URL, hit execute, then wait for scraping + AI + Docs/PDF creation to finish (often around 10–20 minutes). Hands-on time stays close to 5 minutes.
Before You Start
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Decodo Scraper API for fetching Amazon HTML reliably
- Slack to deliver the report to your channel
- OpenAI API key (get it from your OpenAI dashboard)
Skill level: Intermediate. You will connect a few accounts, add API keys, and test with a real Amazon URL.
Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).
Step by Step
You run it with an Amazon URL. The workflow is designed around a manual trigger, so you can test quickly, then later swap in a schedule when you’re ready.
Decodo fetches the page like a real browser. Your chosen device type (desktop/mobile/tablet) matters because Amazon can serve different markup, and Decodo’s headless rendering helps capture late-loading content.
AI extracts clean, structured book data. The HTML is cleaned first, then an AI agent pulls out book objects and validates them through a structured JSON parser so malformed items get dropped instead of breaking your report.
Google Drive and Slack get the finished deliverables. n8n creates a Google Doc in your Drive folder, exports a PDF, then posts it to Slack with a short summary and the doc link for anyone who wants to tweak copy.
You can easily modify the report format to match your brand voice based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Manual Trigger
Start the workflow manually so you can test the full book report pipeline on demand.
- Add the Manual Start Trigger node to initiate the workflow.
- Leave all parameters empty for Manual Start Trigger (default settings).
- Optionally keep Flowpast Branding as a documentation note for the workflow canvas.
Step 2: Connect the Decodo Scraper Input
Provide the scraper token and target URL, then send the request to Decodo for HTML extraction.
- Open Assign Input Fields and set Authenticate_Token to
[CONFIGURE_YOUR_API_KEY]. - Set url to
https://www.amazon.com/Best-Sellers-Books/zgbs/books. - Open Decodo Scraper Call and set url to
=https://www.amazon.com/Best-Sellers-Books/zgbs/booksand geo to=. - Credential Required: Connect your decodoApi credentials in Decodo Scraper Call.
[CONFIGURE_YOUR_API_KEY] with a valid Decodo token, or the scraper request will fail.Step 3: Set Up Text Cleanup and AI Extraction
Clean the raw HTML and extract structured book data using the AI agent and parser.
- Open HTML Text Cleaner and keep the provided jsCode to strip HTML and return plain text.
- In Book Data Analyst, set text to
=Get top 10 best selling book from the below web content:\n{{ $json.text }}. - In Book Data Analyst, confirm systemMessage is
You are a helpful assistant to parse the HTML content and output as well-structure JSONand hasOutputParser is enabled. - Open Structured JSON Parser and paste the schema example exactly as provided to enforce output structure.
- Credential Required: Connect your openAiApi credentials in OpenAI Chat Engine.
Step 4: Configure the Report Composition and Drive File Creation
Convert the AI output into a Markdown report and generate a Google Doc in the correct Drive folder.
- Open Compose 📚 Purchase Report and keep the provided jsCode to build the Markdown report and stats.
- In Set Drive Folder, set Drive Folder ID to
[YOUR_ID]. - In Set Drive Folder, set Today to
{{ $now.format("ddMMyyyyhhmmss") }}. - In Generate Docs File, set url to
https://www.googleapis.com/upload/drive/v3/files?uploadType=multipart&supportsAllDrives=trueand method to POST. - In Generate Docs File, set rawContentType to
multipart/related; boundary=foo_bar_bazand body to the multipart payload using{{ $json.Today }},{{ $json['Drive Folder ID'] }}, and{{ $('Compose 📚 Purchase Report').item.json.markdown }}. - Credential Required: Connect your googleDriveOAuth2Api credentials in Generate Docs File.
[YOUR_ID] with a valid Google Drive folder ID, or the document will be created in the wrong location.Step 5: Configure PDF Export and Slack Delivery
Export the Google Doc to PDF and send it to Slack as a file upload.
- In Export Doc as PDF, set operation to
downloadand fileId to{{ $json.id }}. - Enable Google conversion in Export Doc as PDF so docsToFormat is
application/pdf. - In Post Report to Slack, set resource to
fileand authentication tooAuth2. - Set fileName to
=Book Purchase Report {{ $today.format('yyyy-MM-dd') }}, channelId to[YOUR_ID], and initialComment to📚 Book Purchase Report. - Credential Required: Connect your googleDriveOAuth2Api credentials in Export Doc as PDF.
- Credential Required: Connect your slackOAuth2Api credentials in Post Report to Slack.
[YOUR_ID] in Post Report to Slack with a valid Slack channel ID to avoid file upload errors.Step 6: Test and Activate Your Workflow
Run a manual test to validate the entire pipeline before switching to production use.
- Click Execute Workflow from Manual Start Trigger to run the flow end-to-end.
- Confirm Decodo Scraper Call returns HTML and HTML Text Cleaner outputs a
textfield. - Verify Book Data Analyst returns structured JSON that matches Structured JSON Parser.
- Check that Generate Docs File creates a Google Doc, Export Doc as PDF downloads it, and Post Report to Slack uploads the PDF file.
- When satisfied, toggle the workflow Active to enable production use.
Troubleshooting Tips
- Slack credentials can expire or need specific permissions. If things break, check your Slack app token scopes (files:write and chat:write) 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.
- Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.
Quick Answers
About 30 minutes if your accounts are ready.
No. You’ll mostly paste in API keys, connect Google Drive and Slack, and run a few tests with real URLs.
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 OpenAI API costs (often a few cents per run) and Decodo API usage.
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 you’ll probably want to. Swap the target URL in the “Assign Input Fields” step, then adjust the AI agent’s extraction instructions if you’re scraping something other than books (gadgets, games, office supplies). Common tweaks include changing the recommendation rules in “Compose 📚 Purchase Report,” adding extra fields to the structured JSON schema (like Prime eligibility), and posting to a different Slack channel based on category.
Usually it’s an invalid or expired Decodo API key, or the request is hitting rate limits. Confirm the DECODO_API_KEY value, then check Decodo’s dashboard for blocked requests and concurrency limits. Also verify the Amazon URL is public and accessible, because private lists or region-locked pages can return thin HTML that the extractor can’t work with.
On a typical n8n Cloud plan, you can run thousands of executions per month, and self-hosting has no hard execution cap. In practice, volume depends more on Decodo request limits and how large the pages are. Most teams run this as a daily or weekly report, and it stays stable as long as you keep maxItems reasonable (like 25–100) and avoid firing many runs at once.
Often, yes. This workflow needs a real scraping call, HTML cleanup, structured AI extraction, and document generation, and n8n handles that kind of “messy middle” work cleanly. Zapier or Make can do parts of it, but you may end up stitching together multiple paid steps, plus you’ll hit limits faster when you iterate over items. n8n also gives you self-hosting if you want unlimited executions, which matters once reports become routine. If you only need “send a link to Slack,” keep it simple with another tool. Talk to an automation expert if you’re weighing tradeoffs.
Once this is running, “send the weekly book report” stops being a task someone dreads. The workflow handles the repetitive stuff, and your team gets a clean Doc and PDF right where they already work.
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.
