Block 1 - Image
- Type / Role
- n8n-nodes-base.readWriteFile - readWriteFile
- Config choices
- Version 1
This workflow is provided as-is. Please review and test before using in production.
Multi Photo Facebook Post (Windows Directory) – How to Use Requirements To run this automation, make sure you have the following: n8n installed on your local Windows machine Cloudinary or ...
n8n-nodes-base.readwritefile, n8n-nodes-base.executecommand, n8n-nodes-base.extractfromfile, n8n-nodes-base.code, n8n-nodes-base.merge, n8n-nodes-base.facebookgraphapi, n8n-nodes-base.set, n8n-nodes-base.wait
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by SalmonRK-AI.
Original n8n.io source📘 Multi-Photo Facebook Post (Windows Directory) – How to Use ✅ Requirements To run this automation, make sure you have the following:
✅ n8n installed on your local Windows machine
✅ Cloudinary or any other file hosting service for uploading image files
✅ Facebook Page Access Token with the required permissions (pages_manage_posts, pages_read_engagement, pages_show_list, etc.)
🚀 How to Use Import the provided n8n workflow template into your n8n instance.
Verify the image directory path – ensure that the images you want to post are stored in a local folder (e.g. E:\Autopost-media\YourPage\Images).
Check the caption and hashtag files – this includes:
description.txt (for the post message)
hashtag.txt (for additional tags)
Set your Facebook credentials – insert your Facebook Page Access Token in the designated credential field in the workflow.
⚙️ How It Works (Workflow Logic) Read Text Files
The workflow reads description.txt and hashtag.txt from the local directory.
These are combined to form the message body for the Facebook post.
Select Images to Post
The Limit node defines how many images to post per run (e.g. 3 images).
Selected image files are uploaded to a file server (like Cloudinary) to obtain public URLs.
Post to Facebook (Multi-Photo)
A multi-photo post is created using the uploaded image URLs and the composed message.
Move Posted Images
After the post is successfully published, the original image files are moved to a new folder.
The destination folder is automatically created using the current date (e.g. E:\Autopost-media\YourPage\Images\20250614).
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.
Showing the first 24 of 36 workflow blocks. Download the JSON for the full node graph.
| Workflow | Scheduled multi-photo Facebook posts with Cloudinary from Windows directory |
|---|---|
| Complexity | advanced |
| Nodes | 36 |
| Categories | Social Media |
| Author | SalmonRK-AI |
| Published | 14 Jun 2025 |
Use the JSON export at /data/workflows/4929/4929.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.
Multi Photo Facebook Post (Windows Directory) – How to Use Requirements To run this automation, make sure you have the following: n8n installed on your local Windows machine Cloudinary or ...
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.