HumationHuman + Automation
Back to Catalog

Automate post to multiple Facebook groups with Airtop, Google Sheets & Telegram

Khairul MuhtadinKhairul Muhtadin
386 views
2/3/2026
AnnouncementsGoogle SheetsSlackSchedulerAutomation
Official Page

The Airtop Facebook Automations workflow solves the challenge of managing and posting content across multiple Facebook groups effortlessly. Leveraging Airtop for browser automation, Google Sheets for group management, and Telegram for notifications, this workflow automates posting repetitive updates without manual intervention.

Watch it on work on Youtube

Why Use Airtop Facebook Automations?

💡 Key Benefits:

  • Save Time & Effort: Automate posting to dozens of Facebook groups with a single trigger
  • Consistent Messaging: Avoid errors by automating precise posting steps, ensuring your message appears correctly every time
  • Scalable Engagement: Easily maintain active presence on multiple groups simultaneously, boosting your social reach and brand awareness
  • Integrated Notifications: Receive instant Telegram confirmation for each successful post, keeping you informed without checking Facebook manually

Who Is This For?

⚡ Perfect for:

  • Social media managers looking to scale Facebook group engagement without adding workload
  • Marketing teams aiming to streamline content distribution across communities
  • Small business owners managing Facebook groups for promotional updates
  • Community moderators who post recurring announcements to multiple groups

What Problem Does It Solve?

Posting the same message to many Facebook groups manually is time-consuming, error-prone, and inefficient. Navigating the UI repeatedly can lead to fatigue and missed deadlines. This workflow automates browser interactions linking Telegram-triggered content creation with dynamic group lists from Google Sheets, eliminating manual browser clicking and typing—saving you hours while maintaining consistency and control.

How It Works

🔧 Workflow Steps:

  1. ⏱ Trigger: Listens for new messages in a Telegram chat to capture the post content
  2. 📎 Browser Setup: Initializes the Airtop browser session with a Facebook profile
  3. 🔍 Data Retrieval: Retrieves your list of Facebook groups dynamically from Google Sheets
  4. 🤖 Group Processing: For each group, opens the Facebook group page, scrolls down, and interacts with the post input field
  5. 💌 Publishing: Types and publishes the post, then sends a success message back to Telegram with group details
  6. 🗂 Loop Management: Waits 5 seconds before looping to the next group and closes the browser when done

Setup Instructions

🔐 Getting Started:

1. Import Workflow

Import the provided JSON file into your n8n instance.

2. Set Up Credentials

Configure the following credentials:

  • Airtop API: Requires your API key from airtop.ai
  • Google Sheets OAuth2: To access your Google Sheet with the Facebook group list
  • Telegram API: For message triggers and notifications

3. Customize Workflow Elements

  • Update the Google Sheet URL and sheet name with your group data
  • Adjust the Telegram chat ID or bot to suit your notification preferences
  • Modify post message content as needed via Telegram input

4. Update Required Elements

  • Facebook profile login embedded within Airtop credentials
  • URLs for targeted Facebook group pages must match your groups

5. Test Thoroughly

Test your workflow using realistic group URLs and Telegram messages.

Pre-Requirements

🧩 What You Need:

  • Active n8n instance (Cloud or Self-hosted)
  • Airtop account API key
  • Google account with access to the group list spreadsheet
  • Telegram bot and chat set up for sending and receiving messages

Customization Options

🛠️ Extend the Workflow:

  • Integrate scheduling nodes to automate posts at specific times of day
  • Add error handling to skip groups if the post fails and log results
  • Extend support to Facebook pages or event posting for broader social media management

Technical Details

🧠 Nodes Used:

  • Telegram Trigger: Captures incoming messages
  • Set: Prepares post content
  • Airtop: Handles browser automation (Start Browser, Load URL, Interactions like scroll, click, type, publish)
  • Google Sheets: Fetches group list
  • SplitInBatches: Iterates over each group
  • Telegram: Sends success messages
  • Wait: Manages pacing between posts

Support

📞 Get Help:

  • Made by: Khmuhtadin
  • Tags: Automation, Facebook, Social Media, Airtop, Telegram, Google Sheets
  • Category: Social Media Automation
  • Custom Solutions: Contact Me

Automate Post to Multiple Facebook Groups with Airtop, Google Sheets & Telegram

This n8n workflow automates the process of fetching data from Google Sheets, transforming it, and sending it to Airtop (likely for posting to Facebook groups) while providing updates via Telegram. It's designed to streamline content distribution and keep you informed of the process.

What it does

This workflow simplifies and automates the following steps:

  1. Triggers on Telegram Message: The workflow is manually initiated by a message received in a configured Telegram bot.
  2. Fetches Data from Google Sheets: It reads data from a specified Google Sheet, likely containing the content to be posted and target Facebook groups.
  3. Edits and Transforms Data: The fetched data is then processed and transformed using the "Edit Fields (Set)" node, preparing it for Airtop.
  4. Loops Over Items: The workflow iterates through each item (e.g., each post) retrieved from Google Sheets.
  5. Posts to Airtop: For each item, it sends the processed data to Airtop, which is presumably configured to handle posting to multiple Facebook groups.
  6. Introduces a Delay: A "Wait" node is inserted to pause the workflow between posts, preventing rate-limiting issues or overwhelming the target platforms.
  7. Sends Telegram Notification: After processing each item, a notification is sent via Telegram, indicating the status or completion of the post.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance to import and execute the workflow.
  • Google Sheets Account: Access to a Google Sheet containing the data you wish to automate.
  • Airtop Account: An Airtop account with the necessary configurations for posting to Facebook groups.
  • Telegram Bot: A Telegram bot configured to act as a trigger and send notifications. You will need the bot token and chat ID.

Setup/Usage

  1. Import the Workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Google Sheets: Set up your Google Sheets credentials (OAuth 2.0 or API Key) to allow n8n to read from your spreadsheet.
    • Airtop: Configure your Airtop credentials (API Key or OAuth) to enable n8n to send data to it.
    • Telegram: Set up your Telegram Bot credentials (Bot Token) for both the "Telegram Trigger" and "Telegram" nodes.
  3. Customize Nodes:
    • Google Sheets: Specify the Spreadsheet ID and Sheet Name from which to read your data.
    • Edit Fields (Set): Adjust the fields and expressions to transform your Google Sheet data into the format required by Airtop.
    • Airtop: Configure the Airtop node with the specific operation and data mapping to create posts.
    • Wait: Adjust the delay duration as needed to comply with API rate limits or desired pacing.
    • Telegram: Customize the message content for notifications, perhaps including details about the posted content.
  4. Activate the Workflow: Once configured, activate the workflow. It will now listen for messages on your Telegram bot.
  5. Trigger the Workflow: Send a message to your configured Telegram bot to initiate the workflow and start the automated posting process.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942