Automate Chinese language teaching posts on Facebook with Gemini & Recraft.ai
Workflow Overview
This workflow automates the process of creating and publishing engaging Facebook posts that teach Chinese words to a Thai-speaking audience. It integrates multiple AI models, APIs, and tools to generate content, create visuals, and publish posts seamlessly. Below is a detailed breakdown of the workflow:
Who Is This Template For?
- Social Media Managers: Teams managing Facebook pages and looking for automated, engaging content creation.
- Content Creators: Professionals who want to streamline the process of generating educational and visually appealing posts.
- Language Enthusiasts: Individuals or organizations teaching languages (e.g., Chinese) to a Thai-speaking audience.
What Problem Does This Workflow Solve?
Creating engaging social media content manually can be time-consuming and inconsistent. This workflow solves that by:
- Automating the generation of educational posts in Thai with Chinese vocabulary.
- Creating visually appealing images tailored to the post's theme.
- Publishing posts directly to Facebook using the Pages API.
What This Workflow Does
- Input Handling The workflow starts with an input word (e.g., received via chat or fetched from a Google Sheet). The input is split into two variables (word and input) to ensure data persistence throughout the workflow.
- Generate Text Content An AI model (OpenRouter Chat Model) generates a structured Facebook post in Thai, including:
- Engaging hook
- Core vocabulary (Chinese word, Pinyin, and Thai meaning)
- Real-world usage examples
- Pro-tip or fun fact
- Call-to-action for engagement
- Relevant hashtags
- Describe Image Concept Another AI model creates a brief description of the visual theme for the post. This description is used as input for generating an image.
- Generate Image The workflow uses Recraft.ai to generate an image based on the description. The image is styled consistently using predefined themes (e.g., digital illustration).
- Publish Post The generated text and image are published to Facebook using the Pages API. The post includes: The educational content as the caption. The generated image as the visual element.
Setup Guide
Pre-Requisites
Access to the following APIs:
- OpenRouter.ai: For generating text content and image descriptions.
- Recraft.ai: For generating images.
- Facebook Graph API: For publishing posts.
Step-by-Step Setup
- Configure Input Source: Replace the chat input node with your preferred source (e.g., Google Sheet, email, or manual input). Set Up OpenRouter.ai:
- Configure the credentials for OpenRouter.ai in the respective nodes (OpenRouter Chat Model and OpenRouter Chat Model1).
- Set Up Recraft.ai: Add your API key for Recraft.ai in the Generate Image (Recraft.ai) node.
- Configure Facebook Graph API: Set up the Facebook Graph API credentials with the required permissions (pages_manage_posts, pages_read_engagement, etc.).
- Update the page_id and graphApiVersion in the Facebook Graph API node.
- Test the Workflow: Run the workflow manually to verify that it generates content, creates images, publishes posts, and logs details correctly.
How to Customize This Workflow to Your Needs
- Change Input Source: Replace the chat input with a Google Sheet, email, or database query.
- Modify Content Style: Adjust the AI prompts to suit your audience (e.g., professional tone, casual language).
- Use Different Image Styles: Experiment with other styles/themes in Recraft.ai for the generated images.
- Expand Use Cases: Adapt the workflow to other social media platforms (e.g., Instagram, LinkedIn) by modifying the API calls.
Why Use This Template?
- Efficiency: Automates repetitive tasks like content creation and image generation. Consistency: Ensures posts follow a consistent format and style.
- Engagement: Creates visually appealing and interactive content to boost audience engagement.
- Scalability: Easily adaptable for different topics, languages, or platforms. Additional Resources
Automate Chinese Language Teaching Posts on Facebook with Gemini and RecraftAI
This n8n workflow automates the creation and posting of engaging Chinese language teaching content to a Facebook page. It leverages AI models (Gemini via OpenRouter) to generate post content and a hypothetical "RecraftAI" (represented by an HTTP Request) to create accompanying images, ensuring a consistent and automated content pipeline.
What it does
This workflow streamlines the process of generating and publishing educational content:
- Triggers on Chat Message: The workflow is manually initiated by sending a chat message, which serves as a prompt for the AI to generate content.
- Generates Post Content with AI: An AI Agent, powered by a Chat Model (OpenRouter/Gemini), takes the chat message as input and generates a structured JSON output containing the Facebook post text and a description for an image.
- Parses AI Output: A Structured Output Parser extracts the generated post text and image description from the AI's response.
- Creates Image with RecraftAI: An HTTP Request node simulates an interaction with a "RecraftAI" service, sending the generated image description to create an image.
- Posts to Facebook: Finally, the workflow uses the Facebook Graph API to publish the generated text content and the (simulated) image URL to a specified Facebook page.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running n8n instance.
- OpenRouter API Key: For the "OpenRouter Chat Model" node to access AI models like Gemini.
- Facebook Page Access Token: A Facebook Page Access Token with sufficient permissions to post to your desired Facebook page.
- RecraftAI (or similar image generation service): This workflow includes an HTTP Request node configured to interact with a hypothetical "RecraftAI" endpoint. You will need to replace this with your actual image generation service's API endpoint and authentication details. The current setup is a placeholder.
Setup/Usage
- Import the Workflow: Download the JSON provided and import it into your n8n instance.
- Configure Credentials:
- OpenRouter Chat Model: Set up an OpenRouter credential with your API key.
- Facebook Graph API: Set up a Facebook Graph API credential with your Facebook Page Access Token.
- Customize RecraftAI Integration:
- Open the "HTTP Request" node (labeled "HTTP Request").
- Update the
URLto your actual image generation service's API endpoint. - Adjust the
HeadersandBodyto match the requirements of your chosen image generation service, including any necessary API keys or authentication. - Ensure the node correctly extracts the image URL from the response.
- Configure Facebook Page:
- Open the "Facebook Graph API" node.
- Enter the
Page IDof your Facebook page where the posts should be published.
- Activate the Workflow: Once all credentials and configurations are set, activate the workflow.
- Trigger the Workflow: Send a chat message to the n8n Chat Trigger to initiate the content generation and posting process. The content of the chat message will serve as the prompt for the AI.
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.
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
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.