Block 1 - Set Parameter
- Type / Role
- n8n-nodes-base.set - set
- Config choices
- Version 3.4
This workflow is provided as-is. Please review and test before using in production.
Get Long Lived Facebook Page Access Token with Data Table Set up n8n self hosted via Tino.vn VPS — use code VPSN8N for up to 39% off (affiliate link) . Goo...
n8n-nodes-base.set, n8n-nodes-base.splitout, n8n-nodes-base.datatable, n8n-nodes-base.scheduletrigger, n8n-nodes-base.stickynote, n8n-nodes-base.httprequest
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Đỗ Thành Nguyên.
Original n8n.io source> Set up n8n self-hosted via Tino.vn VPS — use code VPSN8N for up to 39% off (affiliate link).
This workflow automatically solves the common issue of Facebook Page Access Tokens expiring. It proactively renews your Page Tokens and stores them in an n8n Data Table.
It runs every two months, ensuring your Page Access Tokens remain valid. This guarantees seamless and uninterrupted automation for all your Facebook API integrations.
The workflow performs the following steps to keep your tokens up to date:
client_id, client_secret, a short-lived user_access_token, and the app_scoped_user_id (all obtained from Facebook Developer Tools).access_token, name, and id, then performs an Upsert operation to update or insert rows in your n8n Data Table, ensuring the stored tokens are always current.Import: Import this JSON file into your n8n instance.
Configure Credentials: Open the Set Parameters node and replace the placeholder values for client_id, client_secret, user_access_token, and app_scoped_user_id with your actual credentials from Facebook.
Configure Data Table: Open the Upsert row(s) node.
token, name_page, id_page) matches your table schema.Activate: Save and activate the workflow. It will now run automatically based on your configured schedule.
n8n instance : > Set up n8n self-hosted via Tino.vn VPS — use code VPSN8N for up to 39% off (affiliate link).
Facebook App: A Facebook Developer App to generate the following credentials:
client_id and client_secretuser_access_tokenapp_scoped_user_idData Table: An n8n Data Table configured with columns to store token information (e.g., token, name_page, id_page).
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.
| Workflow | Automate Facebook page token renewal with data tables storage |
|---|---|
| Complexity | intermediate |
| Nodes | 12 |
| Categories | Social Media |
| Author | Đỗ Thành Nguyên |
| Published | 22 Oct 2025 |
Use the JSON export at /data/workflows/10038/10038.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
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.
Get Long Lived Facebook Page Access Token with Data Table Set up n8n self hosted via Tino.vn VPS — use code VPSN8N for up to 39% off (affiliate link) . Goo...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
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 Social Media use case.