Back to Catalog

Amazon affiliate marketing automation

Rakin JakariaRakin Jakaria
7052 views
2/3/2026
Official Page

Who this is for

This workflow is for Amazon affiliate marketers and social media managers who want to quickly turn product links into engaging Facebook posts with AI-generated captions and images — fully automated.


What this workflow does

This workflow starts every time a new Product Link is added to a connected Google Sheet. It then:

  • Extracts the ASIN from the product link.
  • Fetches product details from Amazon using RapidAPI.
  • Generates a short, scroll-stopping Facebook caption with OpenRouter AI.
  • Creates a product image prompt and sends it to Google Gemini for high-quality image generation.
  • Uploads the creative directly to Facebook via the Facebook Graph API.
  • Marks the Google Sheet row as “Done ✅” after posting.

The Facebook post includes:

  • Product image (AI-enhanced)
  • Short, benefit-focused caption with emojis
  • Affiliate link

Setup

To set this template up, follow the sticky notes inside the workflow and:

  1. Google Sheets → Connect your sheet and ensure the columns “Product Link” & “Facebook Upload” exist.
  2. RapidAPI → Add your API key in the “Amazon Product Details” node.
  3. OpenRouter → Add credentials for caption generation.
  4. Google Gemini → Add your API key for image generation.
  5. Facebook Graph API → Connect your Facebook account for posting.

How to customize this workflow to your needs

  • Change the Facebook caption prompt to match your tone or branding.
  • Adjust the AI image generation prompt to fit your preferred photography style.
  • Modify the Google Sheet update logic if you want to track additional info (e.g., posting date, engagement stats).
  • Switch Facebook posting to Instagram or another platform by replacing the final API call.

n8n Amazon Affiliate Marketing Automation Workflow

This n8n workflow automates the process of generating and publishing Amazon affiliate product posts to a Facebook page, leveraging AI to create engaging content. It's designed to help affiliate marketers efficiently manage their social media presence and promote products.

What it does

This workflow streamlines your Amazon affiliate marketing efforts by:

  1. Triggering from Google Sheets: It starts by monitoring a specified Google Sheet for new or updated product entries.
  2. Generating Product Content with AI: For each new product, an AI Agent (powered by OpenRouter Chat Model) is used to generate engaging content suitable for a social media post.
  3. Making an Amazon API Request: It then uses an HTTP Request node to interact with the Amazon Product Advertising API (or a similar affiliate API) to fetch product details, including affiliate links and images.
  4. Preparing Content for Facebook: The generated AI content and Amazon product details are combined and formatted into a cohesive post.
  5. Publishing to Facebook: The final post, including the product image and affiliate link, is published to a designated Facebook page using the Facebook Graph API.
  6. Storing Binary Data (Optional/Helper): A "Convert to File" node is present, which might be used for handling binary data like images, potentially converting them for upload or storage.
  7. Implementing Delays: A "Wait" node is included to introduce pauses between operations, which can be useful for respecting API rate limits or scheduling posts.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • Google Sheets Account: Configured with a sheet containing your product data.
  • Amazon Product Advertising API Account: Or access to a similar affiliate product API that can provide product details and affiliate links.
  • OpenRouter Account: For the AI Agent to function, you'll need an OpenRouter API key and potentially access to specific chat models.
  • Facebook Page: A Facebook page where the affiliate posts will be published.
  • Facebook Graph API Credentials: An access token with the necessary permissions to post to your Facebook page.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Google Sheets Trigger:
    • Set up the "Google Sheets Trigger" node to monitor your desired Google Sheet for new rows or updates.
    • Provide the necessary Google Sheets credentials.
  3. Configure AI Agent:
    • Set up the "AI Agent" node with your OpenRouter credentials.
    • Ensure the "OpenRouter Chat Model" node is configured with your OpenRouter API key and the desired model.
    • Adjust the prompt to guide the AI in generating suitable marketing copy for your products.
  4. Configure HTTP Request:
    • Set up the "HTTP Request" node to call the Amazon Product Advertising API (or your chosen affiliate API).
    • Ensure proper authentication (e.g., API keys, signatures) and parameter mapping to fetch product details using data from Google Sheets.
  5. Configure Facebook Graph API:
    • Set up the "Facebook Graph API" node with your Facebook credentials and page ID.
    • Map the output from the AI Agent and HTTP Request nodes to create the post content, including the generated text, product image URL, and affiliate link.
  6. Review and Activate:
    • Inspect all nodes to ensure data mapping and configurations are correct.
    • Test the workflow with sample data.
    • Activate the workflow to start automating your Amazon affiliate marketing posts.

Related Templates

Two-way property repair management system with Google Sheets & Drive

This workflow automates the repair request process between tenants and building managers, keeping all updates organized in a single spreadsheet. It is composed of two coordinated workflows, as two separate triggers are required — one for new repair submissions and another for repair updates. A Unique Unit ID that corresponds to individual units is attributed to each request, and timestamps are used to coordinate repair updates with specific requests. General use cases include: Property managers who manage multiple buildings or units. Building owners looking to centralize tenant repair communication. Automation builders who want to learn multi-trigger workflow design in n8n. --- ⚙️ How It Works Workflow 1 – New Repair Requests Behind the Scenes: A tenant fills out a Google Form (“Repair Request Form”), which automatically adds a new row to a linked Google Sheet. Steps: Trigger: Google Sheets rowAdded – runs when a new form entry appears. Extract & Format: Collects all relevant form data (address, unit, urgency, contacts). Generate Unit ID: Creates a standardized identifier (e.g., BUILDING-UNIT) for tracking. Email Notification: Sends the building manager a formatted email summarizing the repair details and including a link to a Repair Update Form (which activates Workflow 2). --- Workflow 2 – Repair Updates Behind the Scenes:\ Triggered when the building manager submits a follow-up form (“Repair Update Form”). Steps: Lookup by UUID: Uses the Unit ID from Workflow 1 to find the existing row in the Google Sheet. Conditional Logic: If photos are uploaded: Saves each image to a Google Drive folder, renames files consistently, and adds URLs to the sheet. If no photos: Skips the upload step and processes textual updates only. Merge & Update: Combines new data with existing repair info in the same spreadsheet row — enabling a full repair history in one place. --- 🧩 Requirements Google Account (for Forms, Sheets, and Drive) Gmail/email node connected for sending notifications n8n credentials configured for Google API access --- ⚡ Setup Instructions (see more detail in workflow) Import both workflows into n8n, then copy one into a second workflow. Change manual trigger in workflow 2 to a n8n Form node. Connect Google credentials to all nodes. Update spreadsheet and folder IDs in the corresponding nodes. Customize email text, sender name, and form links for your organization. Test each workflow with a sample repair request and a repair update submission. --- 🛠️ Customization Ideas Add Slack or Telegram notifications for urgent repairs. Auto-create folders per building or unit for photo uploads. Generate monthly repair summaries using Google Sheets triggers. Add an AI node to create summaries/extract relevant repair data from repair request that include long submissions.

Matt@VeraisonLabsBy Matt@VeraisonLabs
208

Send WooCommerce cross-sell offers to customers via WhatsApp using Rapiwa API

Who Is This For? This n8n workflow enables automated cross-selling by identifying each WooCommerce customer's most frequently purchased product, finding a related product to recommend, and sending a personalized WhatsApp message using the Rapiwa API. It also verifies whether the user's number is WhatsApp-enabled before sending, and logs both successful and unsuccessful attempts to Google Sheets for tracking. What This Workflow Does Retrieves all paying customers from your WooCommerce store Identifies each customer's most purchased product Finds the latest product in the same category as their most purchased item Cleans and verifies customer phone numbers for WhatsApp compatibility Sends personalized WhatsApp messages with product recommendations Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Customer Segmentation: Automatically identifies paying customers from your WooCommerce store Product Analysis: Determines each customer's most purchased product Smart Recommendations: Finds the latest products in the same category as customer favorites WhatsApp Integration: Uses Rapiwa API for message delivery Phone Number Validation: Verifies WhatsApp numbers before sending messages Dual Logging System: Tracks both successful and failed message attempts in Google Sheets Rate Limiting: Uses batching and wait nodes to prevent API overload Personalized Messaging: Includes customer name and product details in messages Requirements WooCommerce store with API access Rapiwa account with API access for WhatsApp verification and messaging Google account with Sheets access Customer phone numbers in WooCommerce (stored in billing.phone field) How to Use — Step-by-Step Setup Credentials Setup WooCommerce API: Configure WooCommerce API credentials in n8n (e.g., "WooCommerce (get customer)" and "WooCommerce (get customer data)") Rapiwa Bearer Auth: Create an HTTP Bearer credential with your Rapiwa API token Google Sheets OAuth2: Set up OAuth2 credentials for Google Sheets access Configure Google Sheets Ensure your sheet has the required columns as specified in the Google Sheet Column Structure section Verify Code Nodes Code (get paying_customer): Filters customers to include only those who have made purchases Get most buy product id & Clear Number: Identifies the most purchased product and cleans phone numbers Configure HTTP Request Nodes Get customer data: Verify the WooCommerce API endpoint for retrieving customer orders Get specific product data: Verify the WooCommerce API endpoint for product details Get specific product recommend latest product: Verify the WooCommerce API endpoint for finding latest products by category Check valid WhatsApp number Using Rapiwa: Verify the Rapiwa endpoint for WhatsApp number validation Rapiwa Sender: Verify the Rapiwa endpoint for sending messages Google Sheet Required Columns You’ll need two Google Sheets (or two tabs in one spreadsheet): A Google Sheet formatted like this ➤ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: Both must have the following headers (match exactly): | name | number | email | address1 | price | suk | title | product link | validity | staus | | ---------- | ------------- | ----------------------------------------------- | ----------- | ----- | --- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | Important Notes Phone Number Format: The workflow cleans phone numbers by removing all non-digit characters. Ensure your WooCommerce phone numbers are in a compatible format. API Rate Limits: Rapiwa and WooCommerce APIs have rate limits. Adjust batch sizes and wait times accordingly. Data Privacy: Ensure compliance with data protection regulations when sending marketing messages. Error Handling: The workflow logs unverified numbers but doesn't have extensive error handling. Consider adding error notifications for failed API calls. Product Availability: The workflow recommends the latest product in a category, but doesn't check if it's in stock. Consider adding stock status verification. Testing: Always test with a small batch before running the workflow on your entire customer list. Useful Links Dashboard: https://app.rapiwa.com Official Website: https://rapiwa.com Documentation: https://docs.rapiwa.com Support & Help WhatsApp: Chat on WhatsApp Discord: SpaGreen Community Facebook Group: SpaGreen Support Website: https://spagreen.net Developer Portfolio: Codecanyon SpaGreen

RapiwaBy Rapiwa
183

Track SDK documentation drift with GitHub, Notion, Google Sheets, and Slack

📊 Description Automatically track SDK releases from GitHub, compare documentation freshness in Notion, and send Slack alerts when docs lag behind. This workflow ensures documentation stays in sync with releases, improves visibility, and reduces version drift across teams. 🚀📚💬 What This Template Does Step 1: Listens to GitHub repository events to detect new SDK releases. 🧩 Step 2: Fetches release metadata including version, tag, and publish date. 📦 Step 3: Logs release data into Google Sheets for record-keeping and analysis. 📊 Step 4: Retrieves FAQ or documentation data from Notion. 📚 Step 5: Merges GitHub and Notion data to calculate documentation drift. 🔍 Step 6: Flags SDKs whose documentation is over 30 days out of date. ⚠️ Step 7: Sends detailed Slack alerts to notify responsible teams. 🔔 Key Benefits ✅ Keeps SDK documentation aligned with product releases ✅ Prevents outdated information from reaching users ✅ Provides centralized release tracking in Google Sheets ✅ Sends real-time Slack alerts for overdue updates ✅ Strengthens DevRel and developer experience operations Features GitHub release trigger for real-time monitoring Google Sheets logging for tracking and auditing Notion database integration for documentation comparison Automated drift calculation (days since last update) Slack notifications for overdue documentation Requirements GitHub OAuth2 credentials Notion API credentials Google Sheets OAuth2 credentials Slack Bot token with chat:write permissions Target Audience Developer Relations (DevRel) and SDK engineering teams Product documentation and technical writing teams Project managers tracking SDK and doc release parity Step-by-Step Setup Instructions Connect your GitHub account and select your SDK repository. Replace YOURGOOGLESHEETID and YOURSHEET_GID with your tracking spreadsheet. Add your Notion FAQ database ID. Configure your Slack channel ID for alerts. Run once manually to validate setup, then enable automation.

Rahul JoshiBy Rahul Joshi
31