Gemini-powered Facebook comment & DM assistant with Notion
What Problem Does It Solve?
Customers often ask product questions or prices in comments.
Businesses waste time replying manually, leading to delays.
Some comments only need a short thank-you reply, while others need a detailed private response.
This workflow solves these by:
Replying with a friendly public comment.
Sending a private message with details when needed.
Handling compliments, complaints, and unclear comments in a consistent way.
How to Configure It
Facebook Setup
Connect your Facebook Page credentials in n8n.
Add the webhook URL from this workflow to your Facebook App/Webhook settings.
AI Setup
Add your Google Gemini API key (or swap for OpenAI/Claude).
The included prompt is generic — you can edit it to match your brand tone.
Optional Logging
If you want to track processed messages, connect a Notion database or another CRM.
How It Works
Webhook catches new Facebook comments.
AI Agent analyzes the comment and categorizes it (question, compliment, complaint, unclear, spam).
Replying:
For questions/requests → public reply + private message with full details.
For compliments → short thank-you reply.
For complaints → apology reply + private message for clarification.
For unclear comments → ask politely if they need help.
For spam/offensive → ignored (no reply).
Replies and messages are sent instantly via the Facebook Graph API.
Customization Ideas
Change the AI prompt to match your brand voice.
Add forwarding to Slack/Email if a human should review certain replies.
Log conversations in Notion, Google Sheets, or a CRM for reporting.
Expand to Instagram or WhatsApp with small adjustments.
If you need any help Get In Touch
Gemini-Powered Facebook Comment/DM Assistant with Notion
This n8n workflow automates the process of generating smart, context-aware responses to Facebook comments and direct messages using Google Gemini AI, and then logs these interactions in Notion. It acts as an intelligent assistant, streamlining social media engagement and record-keeping.
What it does
This workflow is triggered by an external event (likely a Facebook comment or DM) and performs the following steps:
- Receives Incoming Data: It starts by listening for incoming data via a Webhook, which is expected to contain details about a Facebook comment or direct message.
- Extracts & Transforms Data: It processes the incoming data to extract relevant fields, preparing them for AI processing and Notion logging.
- Analyzes and Responds with AI: It sends the extracted message content to a Google Gemini Chat Model via an AI Agent. The AI agent is designed to understand the context and generate an appropriate response.
- Conditional Logic: It includes an "If" node, suggesting that the workflow might branch based on certain conditions (e.g., whether a response was generated, the sentiment of the message, or the type of interaction).
- Posts Response to Facebook: If the conditions are met (e.g., a valid AI response is generated), it uses the Facebook Graph API to post the AI-generated response back to Facebook (either as a comment or a direct message).
- Logs Interaction in Notion: Simultaneously, it logs the entire interaction (original message, AI-generated response, and other relevant details) into a Notion database for record-keeping and analysis.
- Handles Unsuccessful Responses (Implied): The "If" node implies a path for cases where an AI response might not be generated or meet certain criteria, though the specific actions for this path are not detailed in the JSON.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running n8n instance.
- Facebook Graph API Credentials: An Access Token and App Secret for the Facebook Graph API with appropriate permissions to read comments/DMs and post responses.
- Notion API Key & Database ID: An integration token and the ID of the Notion database where interactions will be logged.
- Google Gemini API Key: Credentials for the Google Gemini Chat Model to power the AI responses.
Setup/Usage
- Import the Workflow: Import the provided JSON into your n8n instance.
- Configure Credentials:
- Set up your Facebook Graph API credentials in n8n.
- Set up your Notion credentials in n8n, ensuring the integration has access to the target database.
- Set up your Google Gemini Chat Model credentials in n8n.
- Configure Webhook: Copy the URL from the "Webhook" node. You will need to configure your Facebook application or a custom integration to send comment/DM events to this URL.
- Customize Nodes:
- Edit Fields (Set) (Node 38): Adjust the fields being extracted and transformed to match the structure of the data sent by your Facebook integration.
- AI Agent (Node 1119) & Google Gemini Chat Model (Node 1262): Fine-tune the AI prompt and model parameters to generate responses that align with your brand voice and desired interaction style.
- If (Node 20): Customize the conditions for when a response should be posted to Facebook or logged in Notion.
- Facebook Graph API (Node 314): Ensure the correct API endpoint and parameters are used for posting comments or sending DMs.
- Notion (Node 487): Map the incoming data and AI-generated responses to the appropriate properties in your Notion database.
- Activate the Workflow: Once configured, activate the workflow in n8n.
Related Templates
Automate Dutch Public Procurement Data Collection with TenderNed
TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte
By Wessel Bulte🎓 How to transform unstructured email data into structured format with AI agent
This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From – sender’s email address To – recipient’s email address Subject – email subject line Summary – short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits ✅ Full Automation: Eliminates manual reading and data entry from incoming emails. ✅ Multi-Source Integration: Handles data from different email providers seamlessly. ✅ AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. ✅ Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. ✅ Time Efficiency: Processes emails in real time, improving productivity and response speed. *✅ Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.
By DavideAutomate RSS to social media pipeline with AI, Airtable & GetLate for multiple platforms
Overview Automates your complete social media content pipeline: sources articles from Wallabag RSS, generates platform-specific posts with AI, creates contextual images, and publishes via GetLate API. Built with 63 nodes across two workflows to handle LinkedIn, Instagram, and Bluesky—with easy expansion to more platforms. Ideal for: Content marketers, solo creators, agencies, and community managers maintaining a consistent multi-platform presence with minimal manual effort. How It Works Two-Workflow Architecture: Content Aggregation Workflow Monitors Wallabag RSS feeds for tagged articles (to-share-linkedin, to-share-instagram, etc.) Extracts and converts content from HTML to Markdown Stores structured data in Airtable with platform assignment AI Generation & Publishing Workflow Scheduled trigger queries Airtable for unpublished content Routes to platform-specific sub-workflows (LinkedIn, Instagram, Bluesky) LLM generates optimized post text and image prompts based on custom brand parameters Optionally generates AI images and hosts them on Imgbb CDN Publishes via GetLate API (immediate or draft mode) Updates Airtable with publication status and metadata Key Features: Tag-based content routing using Wallabag's native system Swappable AI providers (Groq, OpenAI, Anthropic) Platform-specific optimization (tone, length, hashtags, CTAs) Modular design—duplicate sub-workflows to add new platforms in \~30 minutes Centralized Airtable tracking with 17 data points per post Set Up Steps Setup time: \~45-60 minutes for initial configuration Create accounts and get API keys (\~15 min) Wallabag (with RSS feeds enabled) GetLate (social media publishing) Airtable (create base with provided schema—see sticky notes) LLM provider (Groq, OpenAI, or Anthropic) Image service (Hugging Face, Fal.ai, or Stability AI) Imgbb (image hosting) Configure n8n credentials (\~10 min) Add all API keys in n8n's credential manager Detailed credential setup instructions in workflow sticky notes Set up Airtable database (\~10 min) Create "RSS Feed - Content Store" base Add 19 required fields (schema provided in workflow sticky notes) Get Airtable base ID and API key Customize brand prompts (\~15 min) Edit "Set Custom SMCG Prompt" node for each platform Define brand voice, tone, goals, audience, and image preferences Platform-specific examples provided in sticky notes Configure platform settings (\~10 min) Set GetLate account IDs for each platform Enable/disable image generation per platform Choose immediate publish vs. draft mode Adjust schedule trigger frequency Test and deploy Tag test articles in Wallabag Monitor the first few executions in draft mode Activate workflows when satisfied with the output Important: This is a proof-of-concept template. Test thoroughly with draft mode before production use. Detailed setup instructions, troubleshooting tips, and customization guidance are in the workflow's sticky notes. Technical Details 63 nodes: 9 Airtable operations, 8 HTTP requests, 7 code nodes, 3 LangChain LLM chains, 3 RSS triggers, 3 GetLate publishers Supports: Multiple LLM providers, multiple image generation services, unlimited platforms via modular architecture Tracking: 17 metadata fields per post, including publish status, applied parameters, character counts, hashtags, image URLs Prerequisites n8n instance (self-hosted or cloud) Accounts: Wallabag, GetLate, Airtable, LLM provider, image generation service, Imgbb Basic understanding of n8n workflows and credential configuration Time to customize prompts for your brand voice Detailed documentation, Airtable schema, prompt examples, and troubleshooting guides are in the workflow's sticky notes. Category Tags social-media-automation, ai-content-generation, rss-to-social, multi-platform-posting, getlate-api, airtable-database, langchain, workflow-automation, content-marketing
By Mikal Hayden-Gates