🔓 Unlock all 10,000+ workflows & prompts free Join Newsletter →
✅ Full access unlocked — explore all 10,000 AI workflow and prompt templates Browse Templates →
Home › n8n › Workflow
January 22, 2026

Messenger to Slack, approved replies and Sheets logs

Messenger to Slack, approved replies and Sheets logs - n8n workflow automation template
Lisa Granqvist Partner Workflow Automation Expert
Messenger to Slack, approved replies and Sheets logs - n8n workflow automation template
Get a free AI assessment → Get a free AI assessment → ⬇️ Use template

Your Facebook Messenger inbox starts out manageable. Then a promo runs, a post goes semi-viral, or you launch a new offer. Suddenly you’re skimming dozens of DMs, guessing what’s urgent, copying details into notes, and still missing a few that mattered.

This is exactly what marketing managers feel during campaigns, and it hits support leads on busy days too. Even small business owners get dragged into it because nobody wants leads or legit questions sitting unanswered. With this Messenger Slack approval automation, messages get triaged, replies get drafted, and nothing goes out until your team approves it.

You’ll see how the workflow sorts Messenger DMs into Lead, Query, or Spam, routes the right ones to Slack for sign-off, replies only after approval, and logs every interaction to Google Sheets.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: Messenger to Slack, approved replies and Sheets logs

The Problem: Messenger DMs Turn Into a Mess

Messenger is great for engagement, but terrible as a “system.” Leads, real support questions, random “hi,” and spam all land in the same place, and it’s on you to figure it out. The manual triage is where time disappears: you read, interpret intent, decide who should answer, try to match your brand voice, then remember to follow up. And when someone on the team replies quickly but inconsistently, you get avoidable back-and-forth (or worse, a screenshot-worthy mistake). It’s exhausting, honestly.

The friction compounds. Here’s where it breaks down most teams.

  • You spend about 1–2 minutes per message just deciding what it is, and the backlog grows fast when DMs spike.
  • Replies come from different people with different tone, so customers get mixed signals and your brand voice drifts.
  • Approvals happen in scattered places (DMs, screenshots, “can you check this?”), which slows response time.
  • There’s no clean record of what was asked, what you answered, and whether it was handled, so reporting is guesswork.

The Solution: AI Triage + Slack Approval + Sheets Logging

This workflow turns your Messenger inbox into a simple, repeatable process. Every hour, n8n checks your Facebook Page conversations, pulls new messages, and formats the sender details and message text so it’s ready for analysis. Then GPT-4 categorizes each message as a Lead, Query, or Spam and drafts a suggested reply using a structured format, so the “AI output” is consistent and usable. Leads and queries get posted into Slack for a quick approval decision. Once approved, the workflow replies in Messenger automatically and logs the full interaction in Google Sheets, including the category and approval status. If something breaks, you still hear about it because errors trigger an alert in Slack.

The workflow starts on a schedule (hourly) and pulls in new Messenger messages through the Facebook Graph API. GPT-4 handles intent detection and draft replies, then Slack acts as the checkpoint before anything is sent. Finally, Google Sheets becomes your source of truth for tracking.

What You Get: Automation vs. Results

Example: What This Looks Like

Say your Page gets about 40 DMs a day after a campaign. Manually, if you spend just 2 minutes reading and sorting each one, that’s about 80 minutes before you even start replying, plus another 2–3 minutes to draft a decent response and double-check it. With this workflow, the “sorting + draft” part happens automatically during the hourly run, and your team only spends time approving the messages that matter. If approvals take 20–30 seconds each for the 10–15 real leads and queries, you’re usually looking at roughly 10 minutes of focused work instead of a daily inbox slog.

What You’ll Need

  • n8n instance (try n8n Cloud free)
  • Self-hosting option if you prefer (Hostinger works well)
  • Facebook Graph API to fetch and reply to Page DMs.
  • Slack to approve replies in one channel.
  • Google Sheets to log messages and outcomes.
  • OpenAI API key (get it from the OpenAI dashboard).

Skill level: Intermediate. You’ll connect accounts, set a few environment variables (IDs), and test the approval loop end-to-end.

Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).

How It Works

Hourly inbox check. The schedule trigger runs once an hour and calls the Facebook Graph API to retrieve your latest Page conversations, so you’re not relying on someone to “remember to check.”

Message packaging for analysis. n8n extracts the sender, timestamp, and message body, then formats it into a clean payload. This sounds small, but it’s what makes the next step reliable.

AI categorization and draft replies. A GPT-4 powered agent classifies the message as Lead, Query, or Spam and returns structured output (category plus suggested response). That output gets routed through a switch, so each type follows the right path.

Slack approval, Messenger reply, Sheets tracking. Leads and queries are posted to Slack for a decision, then the workflow replies on Messenger only when approval comes through. Every outcome is logged in Google Sheets: approved, pending/fallback, or spam.

You can easily modify the categories (Lead/Query/Spam) to match your business and change the Slack message format to include things like order IDs or campaign tags. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Schedule Trigger

This workflow checks Facebook Messenger conversations on a recurring schedule.

  1. Add the Hourly Messenger Check node as your trigger.
  2. Set the interval rule to run every hour (already configured in the node).
  3. Connect Hourly Messenger Check to Retrieve FB Conversations.

Step 2: Connect Facebook Messenger Retrieval

Pull the latest Messenger conversations and prepare them for AI classification.

  1. Open Retrieve FB Conversations and confirm Edge is set to conversations and Graph API Version to v23.0.
  2. Credential Required: Connect your facebookGraphApi credentials in Retrieve FB Conversations.
  3. In Prepare Message Payload, map fields using expressions:
    • Message → {{ $json.data[0].messages.data[0].message }}
    • Senders Name → {{ $json.data[0].messages.data[0].from.name }}
    • Sender Email → {{ $json.data[0].messages.data[0].from.email }}
    • Created Time → {{ $json.data[0].messages.data[0].created_time }}
    • Senders ID → {{ $json.data[0].messages.data[0].from.id }}
  4. Connect Retrieve FB Conversations → Prepare Message Payload → Classify Messenger Text.

⚠️ Common Pitfall: The Facebook nodes include an access_token query parameter with an empty value. Ensure your Facebook credentials provide a valid token for API calls.

Step 3: Set Up AI Classification

Use the AI agent to classify messages into Lead, Query, or Spam and generate a suggested reply.

  1. Open Classify Messenger Text and verify the Text prompt uses the expressions:
    • {{ $json["Message"] }}
    • {{ $json["Senders Name"] }}
    • {{ $json["Sender Email"] }}
    • {{ $json["Created Time"] }}
  2. Ensure Classify Messenger Text has output parsing enabled and its system message matches your classification rules.
  3. Connect GPT-4 Chat Model as the language model for Classify Messenger Text. Credential Required: Connect your openAiApi credentials in GPT-4 Chat Model.
  4. Attach Context Memory Buffer and set Session Key to "Message Categorization". Add any credentials to the parent Classify Messenger Text node if needed.
  5. Attach Parse AI JSON Result with the provided schema example. Add any credentials to the parent Classify Messenger Text node if needed.

Step 4: Configure Routing and Slack Approvals

Route AI output by category and request approvals for Lead and Query replies.

  1. In Route by Category, confirm the rules match:
    • Lead: {{ $json.output.category }} equals Lead
    • Query: {{ $json.output.category }} equals Query
    • Spam: {{ $json.output.category }} equals Spam
  2. Connect the Lead route to Slack Lead Approval and the Query route to Slack Query Approval; Spam goes directly to Sheets Log Spam.
  3. Credential Required: Connect your slackApi credentials in both Slack Lead Approval and Slack Query Approval.
  4. Verify both Slack nodes use Operation = sendAndWait for approval capture.
  5. Confirm Slack Lead Approval → Verify Lead Decision and Slack Query Approval → Verify Query Decision.

Step 5: Configure Facebook Replies and Google Sheets Logs

Send approved or fallback replies and record outcomes in Google Sheets.

  1. In Verify Lead Decision and Verify Query Decision, keep the approval checks:
    • {{ $json.data.approved }} equals true → send approved reply
    • {{ $json.data.approved }} equals false → send fallback reply
  2. For Facebook responses, ensure each node uses:
    • Post Lead Reply and Post Query Reply message value: {{ JSON.stringify({ text: $('Classify Messenger Text').item.json.output.suggested_reply }) }}
    • Send Lead Fallback and Send Query Fallback message value: the configured fallback text
  3. Credential Required: Connect your facebookGraphApi credentials to all Facebook reply nodes (five nodes handle approved and fallback replies).
  4. Set all Google Sheets logging nodes to Operation appendOrUpdate and confirm the mapping values use expressions like:
    • Summary → {{ $('Classify Messenger Text').item.json.output.summary }}
    • AI Reply → {{ $('Classify Messenger Text').item.json.output.suggested_reply }}
    • Category → {{ $('Classify Messenger Text').item.json.output.category }}
    • Sender ID → {{ $('Prepare Message Payload').item.json["Senders ID"] }}
    • Timestamp → {{ $('Prepare Message Payload').item.json["Created Time"] }}
    • Sender Name → {{ $('Prepare Message Payload').item.json["Senders Name"] }}
  5. Credential Required: Connect your googleSheetsOAuth2Api credentials to all Sheets log nodes (five nodes log Approved, Pending, and Spam outcomes).

⚠️ Common Pitfall: The Google Sheets nodes use matching on Timestamp. Ensure your sheet has matching columns or entries may not update as expected.

Step 6: Add Error Handling

Capture workflow errors and notify your team in Slack.

  1. Confirm Failure Catch Trigger is present and connected to Slack Error Notice.
  2. In Slack Error Notice, keep the Text field set to ❌ *Error in API Error Catalog Workflow* *Node:* {{ $json.node.name }} *Message:* {{ $json.error.message }} *Time:* {{ $json.timestamp }}.
  3. Credential Required: Connect your slackApi credentials in Slack Error Notice.

Step 7: Test and Activate Your Workflow

Run a full test to validate classification, approvals, replies, and logging.

  1. Click Execute Workflow and manually trigger Hourly Messenger Check with a sample conversation.
  2. Confirm Classify Messenger Text outputs category, summary, and suggested_reply, then verify Route by Category routes correctly.
  3. Approve in Slack and verify that Post Lead Reply or Post Query Reply sends a message and logs to the corresponding Sheets node.
  4. Decline approval to confirm Send Lead Fallback or Send Query Fallback is used and logs to the Pending sheets.
  5. Once validation succeeds, toggle the workflow to Active for production use.
🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

  • Facebook Graph API credentials can expire or be missing Page message permissions. If things break, check your Meta App settings and Page access tokens first.
  • If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
  • Slack approvals rely on the right channel and permissions. If approvals don’t route correctly, confirm the channel ID and that your app has chat:write access.

Related Workflows

If your team also needs a lighter-weight version of this idea (AI drafts with a safer manual handoff), Facebook Messenger + OpenAI: replies with safe handoff is a solid companion workflow for testing prompts before you go all-in on approvals and logging.

For teams doing high-volume DM management and wanting more of the replying handled automatically, Facebook Messenger + OpenAI, replies handled for you is useful when you’re confident in your response library and just need exceptions flagged.

When brand reputation is the priority, not just speed, Facebook to Slack, catch negative comments fast pairs well with Messenger automation so your team reacts quickly across both public comments and private DMs.

Need the fastest path to better replies without building a whole approval loop on day one? Facebook Messenger + OpenAI: faster, consistent replies is a nice stepping stone, then you can upgrade to Slack approvals and Sheets logging as volume grows.

Finally, if you want the same “consistent voice + logged responses” pattern for email, Gmail + Google Sheets: consistent auto replies helps you standardize outbound replies and reporting outside social channels.


Quick reference:

Frequently Asked Questions

How long does it take to set up this Messenger Slack approval automation?

About 45 minutes if you already have your API access sorted.

Do I need coding skills to automate Messenger Slack approval?

No. You’ll mainly connect accounts and paste IDs/keys into the right fields. The “logic” is already built into the workflow.

Is n8n free to use for this Messenger Slack approval workflow?

Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in OpenAI API costs (often a few cents per day for typical inbox volume).

Where can I host n8n to run this automation?

Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.

Can I customize this Messenger Slack approval workflow for different categories than Lead/Query/Spam?

Yes, and it’s one of the best tweaks you can make. Update the GPT-4 agent prompt to return your categories (for example: “Pricing,” “Support,” “Partnership,” “Abuse”), then adjust the “Route by Category” switch to match. You can also change the Slack messages to post into different channels per category. Common customizations include adding a “VIP” path, auto-rejecting certain keywords, and writing different log columns in Google Sheets.

Why is my Facebook Graph API connection failing in this workflow?

Usually it’s permissions or an expired token tied to your Facebook app. Confirm your app has Page messaging permissions and that you’re using the right Page ID. If the workflow used to work and suddenly doesn’t, regenerate the access token and update it in n8n. Also watch for message retrieval limits if you’re pulling a lot of conversations at once.

How many messages can this Messenger Slack approval automation handle?

Plenty for most small teams: hundreds of DMs per day is realistic, as long as your Slack approvals and API limits keep up.

Is this Messenger Slack approval automation better than using Zapier or Make?

It depends on how strict you are about control and how messy your inbox gets. n8n is great when you need branching logic (Lead vs Query vs Spam), structured AI output, and a self-host option so you’re not paying more every time volume jumps. Zapier or Make can be faster to start for a simple “new message → send to Slack” flow, but approvals plus logging plus AI categorization gets complicated quickly. Frankly, the approval gate is where many no-code tools start feeling cramped. If you’re unsure, Talk to an automation expert and map it to your exact volume and risk tolerance.

Once this is running, Messenger stops being a daily fire drill. You get cleaner triage, approved replies, and a log you can actually report from.

Need Help Setting This Up?

Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.

Talk to Automation Expert →

Lisa Granqvist

Workflow Automation Expert

Expert in workflow automation and no-code tools.

×

Use template

Get instant access to this n8n workflow Json file

Copy and import json workflow into your n8n workflow

💬
Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.

Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.