Pick a daily Facebook comment contest winner with OpenAI, Airtable and Telegram

16 views

2/3/2026

Placeholder Integration Data Processing Automation Workflow

Community Contest Tracker (FB Comments) → Sentiment Analysis → Telegram Winner Alerts + Airtable Proof

This workflow automatically monitors a Facebook post, extracts comments, enforces a "past winner" blocklist, analyzes sentiment using AI to find positive entries, randomly selects a winner, stores them in Airtable and announces the result via Telegram.

This workflow runs every night to manage your daily community giveaways. It fetches fresh comments from a specific Facebook post and cross-references users against a list of previous winners stored in Airtable to ensure fairness. It uses OpenAI to filter for genuinely positive sentiment (removing spam), selects a random winner, saves the record and sends a celebratory announcement to your Telegram channel.

You receive:

Daily automated comment collection
Fairness enforcement (Blocklist for past winners)
AI-powered sentiment filtering (Positive vibes only)
Automated winner selection & notification

Ideal for community managers and brand owners who want to run fair, high-engagement contests without manually reading hundreds of comments or tracking past winners in spreadsheets.

Quick Start – Implementation Steps

Add your Facebook Graph API Credentials in the HTTP Request node.
Connect and configure your Airtable base (Winners Table).
Add your OpenAI API Key for sentiment analysis.
Connect your Telegram Bot credentials and set the Chat ID.
Update the Post ID in the "Get FB Comments" node.
Activate the workflow — daily contest automation begins instantly.

What It Does

This workflow automates the entire lifecycle of a social media contest:

Daily Trigger: Runs automatically at 9:00 PM every day.
Data Ingestion: Fetches the latest comments from Facebook and the full list of past winners from Airtable simultaneously.
Pre-Processing:
- Creates a blocklist of users who won in the last 30 days.
- Filters out spam, short comments (e.g., single emojis) and blocklisted users.
AI Analysis:
- Uses GPT-4o-mini to analyze the text of eligible comments.
- Filters specifically for "Positive" sentiment.
Selection: Randomly picks one winner from the pool of positive comments.
Storage: Saves the winner's Name, Facebook ID and Comment to Airtable.
Notification:
- Sends a "Winner Announcement" to your public Telegram channel.
- If any errors occur (e.g., DB save fail), logs them to Supabase and alerts the Admin.

This ensures your contests are fair, spam-free and consistently managed with zero manual effort.

Who’s It For

This workflow is ideal for:

Social Media Managers
Community Moderators
Digital Marketing Agencies
Brand Owners running daily giveaways
Influencers managing high-volume comment sections
Customer Experience teams rewarding positive feedback

To run this workflow, you will need

n8n instance (cloud or self-hosted)
Facebook Developer App (Graph API Access Token)
Airtable Base + Personal Access Token
OpenAI API Key (or compatible LLM)
Telegram Bot Token
Supabase Project (Optional, for error logging)

How It Works

Daily Trigger – The schedule node initiates the process.
Fetch Data – Comments are pulled from FB; Winners pulled from Airtable.
Code Filter – JavaScript node removes past winners and low-quality spam.
Sentiment Analysis – AI determines if the comment is Positive, Neutral or Negative.
Pick Winner – A randomized logic block selects one "Positive" user.
Record Keeping – The winner is officially logged in your database.
Broadcast – The winner is announced to the community via Telegram.

Setup Steps

Import the provided n8n JSON file.
Open Get FB Comments node → Add credentials and paste your specific Post ID.
Open Get Past Winners node → Link to your Airtable "Winners" table.
Open OpenAI Chat Model node → Add your API Key.
Open Create a record (Airtable) → Map the fields:
- Name
- Facebook ID
- Date
Open Send a text message (Telegram) → Add your Chat ID (e.g., @mychannel).
Activate the workflow — done!

How To Customize Nodes

Customize Filtering Logic

Modify the Pre-Filter (Blocklist) Code node:

Change the minimum character length (default is 2).
Adjust the "Blocklist" duration (e.g., allow users to win again after 7 days instead of 30).

Customize AI Criteria

Modify the Sentiment Analysis or OpenAI prompt:

Look for "Creative" or "Humorous" comments instead of just "Positive".
Filter for specific keywords related to your brand.

Customize Notifications

Replace Telegram with:

Slack (for internal team updates).
Discord (for gaming communities).
Email (SMTP/Gmail) to notify the marketing team.

Customize Storage

Replace Airtable with:

Google Sheets
Notion
PostgreSQL / MySQL

Add-Ons (Optional Enhancements)

You can extend this workflow to:

Auto-Reply: Use the Facebook API to reply to the winner's comment automatically ("Congrats! DM us to claim.").
Image Generation: Use OpenAI DALL-E or Bannerbear to generate a "Winner Certificate" image.
Cross-Posting: Automatically post the winner's name to Twitter/X or LinkedIn.
Sentiment Report: Create a weekly summary of overall community sentiment (Positive vs Negative ratio).
Prize Tiering: Assign different prizes based on the quality of the comment.

Use Case Examples

1. Daily Product Giveaways

Reward one user every day who comments why they love your product.

2. Feedback Drives

Encourage users to leave constructive feedback and reward the most helpful positive comment.

3. Community Engagement

Keep your group active by automating "Best Comment of the Day" rewards.

4. Brand Loyalty Programs

Track "Super Fans" by counting how many times they participate (even if they don't win).

Troubleshooting Guide

Need Help?

If you need help customizing or extending this workflow, adding multi-platform support (Instagram/YouTube), integrating complex prize logic or setting up advanced dashboards, feel free to hire n8n automation developers at WeblineIndia. We are happy to assist you with advanced automation solutions.

n8n Workflow: Daily Facebook Comment Contest Winner Selection with AI, Airtable, and Telegram

This n8n workflow automates the process of selecting a winner from Facebook comments for a daily contest. It leverages AI for sentiment analysis, stores data in Airtable, and announces the winner via Telegram.

What it does

This workflow streamlines the selection of a contest winner by:

Triggering daily: The workflow is scheduled to run once every day.
Fetching Facebook comments: It retrieves comments from a specified Facebook post (though the Facebook node is not present in the provided JSON, it's implied by the workflow's purpose and the subsequent steps).
Analyzing comment sentiment: Uses OpenAI's language model to perform sentiment analysis on each comment.
Filtering comments: Evaluates if the sentiment analysis was successful and if the comment is positive.
Storing eligible comments in Airtable: If a comment meets the criteria, it's added to an Airtable base, including the comment text, sentiment, and the commenter's name.
Selecting a random winner: (Implied, as the Airtable data is used to pick a winner) From the eligible comments in Airtable, a random winner is selected.
Announcing the winner: Posts the winner's name and a congratulatory message to a Telegram channel.

Prerequisites/Requirements

To use this workflow, you will need:

n8n Instance: A running n8n instance.
Airtable Account: An Airtable account with a base and table configured to store contest comments (e.g., fields for Comment, Sentiment, User Name).
OpenAI API Key: An OpenAI API key for the "OpenAI Chat Model" and "Sentiment Analysis" nodes.
Telegram Bot Token and Chat ID: A Telegram bot and the chat ID of the channel where the winner will be announced.
Facebook Integration (Implied): Although not explicitly in the JSON, a Facebook node would be required to fetch comments from a specific post. This would need appropriate Facebook API access.

Setup/Usage

Import the workflow: Download the JSON and import it into your n8n instance.
Configure Credentials:
- Airtable: Set up your Airtable credential, linking it to your base and table.
- OpenAI: Configure your OpenAI credential with your API key.
- Telegram: Set up your Telegram credential with your bot token and specify the chat ID where the winner announcement should be sent.
Configure Nodes:
- Schedule Trigger: Adjust the schedule to your desired daily frequency (e.g., once a day at a specific time).
- Airtable: Ensure the "Airtable" node is configured to write to the correct base and table, mapping the Facebook comment data (comment text, sentiment, user name) to your Airtable fields.
- OpenAI Chat Model: Review the prompt used for sentiment analysis if you wish to fine-tune its behavior.
- Sentiment Analysis: Verify the output format and how it's interpreted by the "If" node.
- If: Confirm the conditions for filtering comments based on sentiment.
- Code: This node is likely used for selecting a random winner from the Airtable data. Review and adjust the JavaScript code if your Airtable structure or winner selection logic differs.
- HTTP Request: This node might be used for additional API calls related to Facebook or other services. Configure it as needed.
- Telegram: Customize the message sent to Telegram for the winner announcement.
Activate the workflow: Once all configurations are complete, activate the workflow.

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.

By 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

By 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.

By Le Nguyen

942