Sharing an n8n Workflow to Auto-Post to Facebook Pages from Google Sheets

Introduction

If you manage Facebook Pages and often publish posts manually, this n8n workflow may be a practical reference.

The workflow is designed to read data from Google Sheets and automatically publish content to a Facebook Page. The content can be a text post, an image post, a Facebook Reel, or the first comment after publishing.

The main idea behind this workflow is not only “auto-posting.” It is about organizing a small and manageable content system: Google Sheets stores the content, the CONFIG sheet stores Page settings, and n8n handles the repetitive publishing steps in the background.

This workflow has been used in real projects for about 3 months and has been running steadily. Most issues, when they happen, usually come from input data or temporary/API-related changes, not from the core workflow logic.

What is this workflow used for?

This workflow helps automate the process of publishing content from Google Sheets to Facebook Pages.

Main features include:

• Publishing text posts.
• Publishing image posts.
• Publishing Facebook Reels from video files.
• Posting the first comment after a post or Reel is published.
• Updating postid or reel_id back to Google Sheets.
• Managing multiple Pages through a CONFIG sheet.
• Reducing daily manual posting work.

Users only need to prepare the data in Google Sheets. n8n will read the data, select suitable content, publish it to the Facebook Page, and update the status after publishing.

Who should use this workflow?

This workflow is suitable for:

• People managing one or multiple Facebook Pages.
• Affiliate marketers.
• Product content creators.
• Small teams or small businesses that publish content regularly.
• Users learning n8n through a real-world automation example.
• Anyone who wants to combine Google Sheets, Facebook Graph API, and n8n in a practical workflow.

It is especially useful when your content is already prepared in Google Sheets and you want to reduce repetitive manual posting tasks.

How does the workflow work?

The general workflow flow is:

Schedule Trigger
→ Check the posting time
→ Read configuration from Google Sheets
→ Select the appropriate Page
→ Choose the Post or Reel branch
→ Read content data from Google Sheets
→ Publish content to the Facebook Page
→ Update the result back to Google Sheets
→ Publish the first comment

The workflow has two main publishing branches.

Post branch:

• Reads post content from Google Sheets.
• Checks whether the post has images.
• If there are no images, it publishes a text post.
• If there are images, it uploads the images and publishes a post with images.
• Updates postid back to Google Sheets.

Reel branch:

• Reads Reel data from Google Sheets.
• Gets the video file from the local folder.
• Uploads the video to Facebook Reels.
• Updates reel_id back to Google Sheets.

After the post or Reel is published, the workflow can add the first comment, usually used for a link, price, or extra information.

Google Sheet data structure

The workflow uses Google Sheets to store both configuration data and publishing content.

It is recommended to organize the Google Sheet into two main parts:

1. CONFIG sheet

The CONFIG sheet stores Page-level configuration.

Main columns include:

• page_name: Page name for easy identification.
• page_id: Facebook Page ID.
• access_token: Facebook Page Access Token.
• document_id: Google Sheet file ID.
• sheet_id: ID of the post data sheet.
• sheet_reel_id: ID of the Reel data sheet.
• minute_slot: minute range used to select the corresponding Page/config.
• note: internal note.

This structure allows one workflow to work with multiple Pages or different data sheets.

2. Content data sheet

Each data sheet contains a list of content items to publish.

Common columns include:

• message: main post content.
• price: price or additional information, if any.
• link: link used in the comment or post content.
• image1, image2, image3: image URLs.
• video_url: video filename or local video path.
• date: optional note or tracking date.
• postid: automatically updated after a post is published.
• reel_id: automatically updated after a Reel is published.
• commentid: reserved column, not currently used in the default workflow.

Important note: in the current workflow, video_url is used as a local video filename or local path that n8n can read. It is not an online video URL. If you want to use videos from public URLs, you need to modify the video reading or uploading node in the Reel branch.

Requirements before deployment

Before using the workflow, you need to prepare a few basic components.

1. n8n

• An active n8n environment, either cloud or self-hosted.
• Permission to import workflow JSON files.
• Ability to create Google Sheets credentials.
• Ability to call Facebook Graph API using HTTP Request nodes.

2. Google Sheets

• A Google Sheet file that includes the CONFIG sheet and content data sheets.
• Google Sheets credentials with read and write permissions.

3. Facebook Page

• Facebook Page ID.
• A valid Page Access Token.
• Permission to publish posts to the Page.
• Permission to upload images, upload videos, and comment if these features are used.

4. Local video files, if using Reels

• Video files must be stored in a folder that n8n can read.
• If n8n runs in Docker, the video folder must be mounted into the container.
• The filename in Google Sheets must match the actual video file.

Importing and testing the workflow

After downloading the workflow JSON file, you can import it into n8n.

After importing, check the following:

• Google Sheets credentials.
• Facebook API version.
• CONFIG sheet.
• Page ID and Access Token.
• Local video folder path, if using Reels.

Recommended testing order:

Test 1: Text post

• Prepare one row with text content only.
• Run the workflow.
• Check whether the post has been published.
• Check whether postid has been updated.

Test 2: Image post

• Prepare one row with image URLs.
• Run the workflow.
• Check whether the images are displayed correctly.
• Check whether postid has been updated.

Test 3: Reel

• Prepare one video file in the local folder.
• Enter the filename in Google Sheets.
• Run the workflow.
• Check whether the Reel has been published.
• Check whether reel_id has been updated.

Test 4: Comment

• Check whether the first comment is published.
• Check whether the comment includes the correct price, link, or additional information.

Do not activate the workflow immediately after importing it. Test it first with a test Page or test data to avoid posting incorrect content to your main Page.

Common issues

Some common issues may appear during deployment or operation.

Workflow does not run

Possible causes include the workflow not being Active, the schedule not being triggered yet, incorrect time conditions, or timezone mismatch.

CONFIG row cannot be selected

This usually happens when the CONFIG sheet is empty, minute_slot does not match, or document_id / sheet_id is incorrect.

Google Sheets cannot be read

This may be caused by incorrect credentials, missing sharing permission, or an account that does not have write access.

Cannot publish to Facebook

This usually relates to the Access Token. The token may be incorrect, expired, linked to the wrong Page, or missing required permissions.

Image publishing error

This may happen when the image URL is not public, the link has expired, or the image server blocks Facebook from downloading it.

Reel publishing error

Common causes include incorrect video filename, incorrect local path, n8n not being able to read the file, or the video file not being placed in the configured folder.

Post is published but comment fails

The post may not be ready yet, the token may not have comment permission, or the Wait time may be too short.

Google Sheet is not updated

Check row_number, column mapping, write permission, and the Sheet structure.

Practical operation notes

During the first few days, monitor execution logs regularly. This helps you detect duplicate posting, comment errors, image errors, or Sheet update issues early.

Do not change too many parts of the workflow at the same time. If you want to change the schedule, post format, comment format, or video path, make one small change and test again before moving to the next one.

It is also a good idea to keep backup content ready in Google Sheets so the workflow does not run out of valid rows.

Security is important. Do not share workflows or Google Sheets that contain real Access Tokens. If you want to share the workflow publicly, remove tokens, sensitive Page IDs, and private information first.

For workflows using Facebook Graph API, tokens should also be checked periodically. If a token expires or its permission changes, the workflow may stop working even if the workflow logic is still correct.

When should you customize this workflow?

You can customize this workflow if you want to:

• Change the post format.
• Change the comment format.
• Use more columns from Google Sheets.
• Add more image fields.
• Change the posting schedule.
• Separate Post and Reel data into different sheets.
• Use public video URLs instead of local video files.
• Expand the workflow for more Pages.

The included documentation describes the main node groups, making it easier to understand how the workflow works and where to customize it based on your needs.

Final thoughts

This n8n workflow for auto-posting to Facebook Pages from Google Sheets is a practical example of a small but useful automation system.

Instead of publishing posts manually every day, you can use Google Sheets to manage content and let n8n handle the repetitive steps: reading data, publishing posts, uploading Reels, posting comments, and updating status.

The workflow is suitable for Facebook Page managers, affiliate marketers, content creators, and small teams that need to publish content regularly.

You can start with the simplest version: publishing text posts from Google Sheets. Then you can gradually expand it to image posts, Reels, first comments, and multiple Page management with the CONFIG sheet.

Download the document and workflow (JSON) bellow