Get long-lived Facebook Page access tokens and subscribe Messenger webhook fields via Graph API

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

1. Workflow Overview

Get Long Lived Facebook Page Access Token and Subscribe Messenger Webhook Fields This n8n template automates two critical one time setup steps required before any Facebook automation can go live: i...

Best for

Support Chatbot automation workflows
advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.stickynote, n8n-nodes-base.manualtrigger, n8n-nodes-base.set, n8n-nodes-base.httprequest, n8n-nodes-base.splitout, n8n-nodes-base.splitinbatches, n8n-nodes-base.code, n8n-nodes-base.wait

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Nguyễn Thiệu Toàn (Jay Nguyen).

Original n8n.io source

1.1 Workflow description

Title: Get long-lived Facebook Page access tokens and subscribe Messenger webhook fields via Graph API
Workflow name: Get long-lived Facebook Page access tokens and subscribe Messenger webhook fields via Graph API

Get Long-Lived Facebook Page Access Token and Subscribe Messenger Webhook Fields

This n8n template automates two critical one-time setup steps required before any Facebook automation can go live: it exchanges a short-lived User Access Token for a long-lived one (~60 days), retrieves Page Access Tokens for all connected Facebook Pages, and subscribes each Page to the webhook fields your app needs — all in a single manual run.

If you're building a Messenger chatbot or automating comment replies on Facebook Pages, run this utility workflow once as part of your initial setup.

How it works

Needed Value node: Set your app_id, app_secret, short-lived short_user_access_token, and field_to_add (the webhook subscription fields) in one place — no other node needs editing.
Token Exchange: Calls the Facebook Graph API to exchange the short-lived token for a long-lived User Access Token, then resolves the app-scoped User ID.
Page Token Retrieval: Fetches long-lived Page Access Tokens for all Pages connected to this user.
Per-Page Webhook Subscription: Loops through each Page — fetches its existing subscribed fields, merges them with your new fields, and POSTs the combined list back to the Graph API.
Rate Limiting: A 1-second Wait node between each Page prevents hitting Facebook's API rate limits.

How to use

Get credentials: Retrieve your App ID and App Secret from Meta for Developers.
Generate a short-lived token: Use Graph API Explorer with pages_manage_metadata and pages_show_list permissions.
Fill in Needed Value: Enter all four config fields. Set field_to_add based on your use case (e.g., messages,messaging_postbacks for Messenger chatbots, or add feed for comment automation).
Run manually: Click "Execute Workflow". The output of Get long-lived page access token contains the Page Access Token — copy it into your chatbot workflows.

Requirements

n8n Version: Built and tested on n8n 2.9.4+. (It is highly recommended to update to the latest n8n version.)
A Facebook App with Messenger product enabled and pages_manage_metadata permission approved.
No external credentials needed inside n8n — all API calls use the token from the Needed Value node.

Customizing this workflow

Different webhook fields: Update field_to_add — common values: messages, messaging_postbacks, messaging_optins, message_deliveries, feed.
Auto-refresh tokens: Swap the Manual Trigger for a Schedule Trigger every 50 days so your long-lived tokens never expire unexpectedly.
Notify on completion: Add a Telegram or Gmail node after the loop to confirm successful subscription for each Page.

Related workflows by the same author:

About the Author

Created by: Nguyễn Thiệu Toàn (Jay Nguyen) - n8n Verified Creator Email: [email protected] Website: nguyenthieutoan.com Company: GenStaff (CEO/Founder) (genstaff.net) Socials (Facebook / X / LinkedIn): @nguyenthieutoan More templates: n8n.io/creators/nguyenthieutoan

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Main Overview

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 2 - Warning Edit

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 3 - Section 1

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 4 - Section 2

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 5 - Author Message

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 6 - When clicking 'Execute workflow'

Type / Role: n8n-nodes-base.manualTrigger - manualTrigger
Config choices: Version 1

Block 7 - Needed Value

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.4

Block 8 - Get long-lived user access token

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.4

Block 9 - Get app scoped user id

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.4

Block 10 - Get long-lived page access token

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.4

Block 11 - Split Out Pages

Type / Role: n8n-nodes-base.splitOut - splitOut
Config choices: Version 1

Block 12 - Loop Over Items

Type / Role: n8n-nodes-base.splitInBatches - splitInBatches
Config choices: Version 3

Block 13 - GET Current Fields

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.4

Block 14 - Merge Fields

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 15 - POST Merged Fields

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.4

Block 16 - Wait 1s (rate limit)

Type / Role: n8n-nodes-base.wait - wait
Config choices: Version 1.1

Block 17 - Sticky Note

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

3. Summary Table

Workflow	Get long-lived Facebook Page access tokens and subscribe Messenger webhook fields via Graph API
Complexity	advanced
Nodes	17
Categories	Support Chatbot
Author	Nguyễn Thiệu Toàn (Jay Nguyen)
Published	13 Mar 2026

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/14027/14027.json as the source template for this automation.
2. Import the template into n8n

Open n8n, import the downloaded JSON, and review each node before activating the workflow.
3. Configure credentials and variables

Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
4. Test with sample data

Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
5. Activate and monitor

Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Download workflow JSON Original n8n.io source Support Chatbot workflows

Frequently asked questions

What does Get long-lived Facebook Page access tokens and subscribe Messenger webhook fields via Graph API do?

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Support Chatbot use case.

Nguyễn Thiệu Toàn (Jay Nguyen)

20 workflows

Nodes

n8n-nodes-base.stickynote n8n-nodes-base.manualtrigger n8n-nodes-base.set n8n-nodes-base.httprequest n8n-nodes-base.splitout n8n-nodes-base.splitinbatches n8n-nodes-base.code n8n-nodes-base.wait

Complexity

advanced

Published 13 Mar 2026

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/14027/14027.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Route RAG customer support across WhatsApp and Outlook with Pinecone and OpenRouter

## Quick overview A production-ready 3-workflow system that handles customer support across WhatsApp and Email using RAG-powered AI. Automatically routes queries, detects escalation intent, logs handoffs to Google Sheets, alerts your team via Slack, and lets agents resolve cases with a single slash command. ## How it works 1. A form trigger accepts PDF, DOCX, and TXT documents, chunks them with a token splitter, embeds them using Google Gemini, and stores them in your Pinecone vector store to build the AI knowledge base. 2. Incoming messages from WhatsApp Business Cloud API and Microsoft Outlook are each normalized into a unified contact format — capturing channel, contact ID, name, and message text — before merging into a single pipeline. 3. Every message is checked against a Google Sheets handoff tracker. If the contact is currently assigned to a human agent, the message is forwarded directly to Slack without any AI involvement. 4. For active (non-handoff) contacts, the AI Support Agent queries Pinecone via RAG, pulls context from a sliding conversation memory window, and returns a structured JSON output containing a reply and a handoff_requested flag. 5. If the AI detects escalation intent or has no answer, it sets handoff_requested: true — the contact is logged to Google Sheets, AI goes silent for that contact, and a detailed alert is posted to your Slack support channel. 6. Answers are routed back through the originating channel — WhatsApp replies via Business Cloud API, email replies via Microsoft Outlook — keeping every conversation native to its platform. 7. Support agents run /resolve [contact_id] in Slack to close a handoff. The workflow validates the input, updates the Google Sheets row with agent name and timestamp, re-enables AI for that contact, and confirms resolution in the Slack channel. ## Setup 1. Pinecone + Embeddings: Create a Pinecone index and add your Pinecone credential to the "Insert into Vector Store" and "Knowledge Base" nodes. Set your Google Gemini API credential on both Embeddings nodes (one in Workflow 1, one in Workflow 2). 2. WhatsApp: Connect your WhatsApp Business Cloud API credential to the WhatsApp Trigger node. Replace YOUR_WHATSAPP_PHONE_NUMBER_ID in both Send WhatsApp Message nodes. 3. Email: Add your Microsoft Outlook OAuth2 credential to the Outlook Trigger and the Send Email Answer node. 4. Handoff Sheet: Create a Google Sheet with a tab named Handoffs and these column headers exactly: contact_id | channel | contact_name | status | handoff_since | resolved_by | resolved_at. Set your Google Sheets credential and paste your Sheet ID into all four Google Sheets nodes across Workflows 2 and 3. 5. Slack: Create a Slack bot app, add it to your support channel, and set the credential in all three Slack nodes. Update the channel name if yours differs from #support-handoff. 6. AI Model: Add your OpenRouter (or OpenAI) API key to the Chat Model node. Swap the model slug in node settings as needed. 7. Slash Command: Activate Workflow 3 first to generate its production webhook URL. Then in your Slack app settings go to Slash Commands → Create New → set command to /resolve → paste the webhook URL → reinstall app to workspace. 8. Activate order: Workflow 1 (KB ingestion) → Workflow 3 (resolve handler) → Workflow 2 (main support flow). ## Requirements - n8n (self-hosted or cloud) - WhatsApp Business Cloud API account (Meta Developer App) - Microsoft 365 / Outlook account - Pinecone account - Google Gemini API key - OpenRouter or OpenAI API key or Any other LLM - Google Sheets - Slack workspace with a custom bot app ## Customization - Edit the system prompt in the AI Support Agent node to match your brand voice, support scope, and escalation rules - Swap Google Gemini Embeddings for OpenAI Embeddings — just replace the Embeddings node and ensure your Pinecone index dimensions match - dd more channels (Telegram, Instagram DM, etc.) by normalizing their payloads into the same contact format and feeding them into the Merge node - Adjust conversation memory window (default: 8 messages) in the Conversation Memory node - Trigger the resolve webhook from your CRM or helpdesk instead of Slack if preferred ## Additional info All three workflows must be active simultaneously for the system to function Handoff state is persisted in Google Sheets and survives n8n restarts or server reboots Once a contact enters handoff, the AI is completely silent for that contact — no accidental double-responses Document metadata (filename, uploader name, timestamp) is stored alongside vectors in Pinecone for full traceability Default chunk settings: 500 tokens / 100 overlap — tune in the Token Splitter node based on your document style Contact / Support 🔗 n8n Templates: n8n.io/creators/salmanmehboob 💼 LinkedIn: linkedin.com/in/salman-mehboob-pro 📧 Email: [email protected] 💬 WhatsApp: +92 306 746 6499

View

Answer hotel guest messages with GPT-4o mini, Slack, and Google Sheets

## Quick Overview This workflow receives guest messages via a webhook, uses OpenAI (GPT-4o-mini) to generate multilingual hotel support replies with an escalation flag, notifies the front desk in Slack when needed, logs the interaction to Google Sheets, and returns a JSON acknowledgement to the messaging gateway. ## How it works 1. Receives an inbound guest message through a webhook from a WhatsApp/Viber gateway. 2. Normalizes the incoming payload into a consistent structure (guest ID, channel, guest name, and message text). 3. Uses OpenAI (GPT-4o-mini) to generate a short reply in the guest’s language based on the built-in hotel information and outputs structured JSON with language, reply, category, and an escalate flag. 4. If the message needs human attention, posts the guest details and message to a Slack front-desk channel. 5. Routes the reply based on the reported channel and sends the generated reply text to Slack. 6. Appends the conversation data to Google Sheets and responds to the gateway with a JSON status including the detected language and whether it was escalated. ## Setup 1. Configure the inbound webhook URL in your WhatsApp/Viber gateway so it sends a payload containing at least channel, from, and text/message fields. 2. Add OpenAI API credentials for the GPT-4o-mini model. 3. Add Slack OAuth2 credentials and set the target channels for front-desk notifications and reply delivery. 4. Add Google Sheets OAuth2 credentials and update the spreadsheet/document ID and sheet tab used for logging.

View

Answer support questions from a knowledge base with OpenAI GPT-4o-mini

## Quick Overview This workflow powers a support chat experience that uses an OpenAI RAG agent with in-memory vector search to answer questions from a knowledge base, and includes a manual ingestion flow that fetches an external FAQ document, splits it into chunks, embeds it with OpenAI, and stores it for retrieval. ## How it works 1. Triggers when a new chat message is received. 2. Uses an OpenAI chat model with conversation memory to generate a support reply while following the system support guidelines. 3. Creates OpenAI embeddings for the user’s query and searches an in-memory vector knowledge base for the top matching snippets. 4. Uses the retrieved knowledge base content as a tool to ground the final answer and returns the response to the chat. 5. When run manually, fetches FAQ content from a specified URL via HTTP. 6. Splits the fetched text into chunks, converts it into documents, generates OpenAI embeddings, and inserts the vectors into the in-memory knowledge base for future queries. ## Setup 1. Add OpenAI credentials for both chat completions (GPT-4o-mini) and embeddings. 2. Update the source URL in the HTTP Request step (currently https://example.com/help-center/faq.txt) to point to your real FAQ/knowledge base content. 3. Run the manual ingestion flow once to populate the in-memory knowledge base before testing the chat trigger.

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Get long-lived Facebook Page access tokens and subscribe Messenger webhook fields via Graph API

Workflow preview

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

Get Long-Lived Facebook Page Access Token and Subscribe Messenger Webhook Fields

How it works

How to use

Requirements

Customizing this workflow

About the Author

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - Main Overview

Block 2 - Warning Edit

Block 3 - Section 1

Block 4 - Section 2

Block 5 - Author Message

Block 6 - When clicking 'Execute workflow'

Block 7 - Needed Value

Block 8 - Get long-lived user access token

Block 9 - Get app scoped user id

Block 10 - Get long-lived page access token

Block 11 - Split Out Pages

Block 12 - Loop Over Items

Block 13 - GET Current Fields

Block 14 - Merge Fields

Block 15 - POST Merged Fields

Block 16 - Wait 1s (rate limit)

Block 17 - Sticky Note

3. Summary Table

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

2. Import the template into n8n

3. Configure credentials and variables

4. Test with sample data

5. Activate and monitor

5. General Notes & Resources

Frequently asked questions