Reply to Facebook ad comments with OpenRouter AI, Google Docs and Slack
Ready for 3.0What this workflow does
This AI workflow has 14 nodes and runs when an HTTP POST request hits its webhook URL. Along the way it connects OpenRouter Chat Model, Google Docs and Slack.
How it runs
Trigger: When an HTTP POST request hits its webhook URL.
- Filleter Author Comment and Reqular Post (Filter): keeps only the items that match a condition
- Get Commnet Details (HTTP Request): calls an HTTP API
- Skip If Coment Contains Attachment (Switch): routes items into 2 branches
- Get FB Post Data (HTTP Request): calls an HTTP API
- Clean Data (Edit Fields (Set)): sets 6 fields: post_text, post_permalink_url, comment_text…
- Comment Classifier (AI Agent): runs an AI agent, with model: OpenRouter Chat Model; output parser: Structured Output Parser
- Switch: routes items into 4 branches
- Comment Generator (AI Agent): runs an AI agent, with model: OpenRouter Chat Model; 1 tool (Knowledge Base)
- Inform User (Slack): uses Slack
- Reply to Comment (HTTP Request): calls an HTTP API (POST)
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (10)
- Webhook
n8n-nodes-base.webhook - HTTP Request
n8n-nodes-base.httpRequest - OpenRouter Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenRouter - Filter
n8n-nodes-base.filter - Switch
n8n-nodes-base.switch - Edit Fields (Set)
n8n-nodes-base.set - AI Agent
@n8n/n8n-nodes-langchain.agent - Google Docs Tool
n8n-nodes-base.googleDocsTool - Slack
n8n-nodes-base.slack - Structured Output Parser
@n8n/n8n-nodes-langchain.outputParserStructured
From the author
Every comment on your Facebook ad is a sales opportunity. But manually replying to dozens of comments every day - in the right tone, in the right language, at the right speed - is simply not scalable. This workflow deploys an AI agent that watches your…