Multi-Content Instagram Scheduler using Facebook Graph API - n8n Workflow

Social Media Managers needing reliable, scheduled posting.
Automation Specialists looking for complex, real-world n8n templates.
Developers integrating Instagram publishing into larger applications.
Users seeking a robust n8n workflow solution for handling asynchronous API processing (polling).

This comprehensive n8n workflow template solves the complex problem of reliably scheduling diverse Instagram content (images, Reels, stories, carousels) by directly interacting with the Facebook Graph API. The complexity arises because media uploads require two steps: container creation and publication, with a required processing delay between them. This specific n8n workflow incorporates critical status checking and polling mechanisms using Wait and If n8n nodes, ensuring the media container is fully processed and ready by Instagram before attempting publication. This robust setup leverages dynamic routing to support multiple methods (generic HTTP Request n8n node and specialized Facebook Graph API n8n node), making it a powerful foundation for any social media automation pipeline built on n8n.

The entire process is initiated either manually using the 🚀 Manual Trigger - Start Workflow n8n trigger or automatically via a scheduled n8n trigger (if configured for production).

1. Configuration: The ⚙️ Configure Post Settings n8n node defines critical parameters such as the Instagram Business Account ID (node), media URLs, caption, and the crucial posttype (e.g., httpreel, fbimage).


2. Smart Content Routing: The 🔀 Smart Content Router n8n node analyzes the posttype variable to route the flow to the appropriate container creation n8n node (e.g., Container HTTP Reels). Special types like Carousels require chaining multiple container creation n8n nodes before the parent carousel container is created.


3. Container Creation: One of the various specialized container n8n nodes calls the Graph API's /media endpoint, receiving a unique media id (the container ID).


4. The Polling Pipeline: The n8n workflow immediately enters a robust polling loop. The 🔍 Check Processing Status n8n node captures the container ID, waits using the ⏰ Initial Processing Wait n8n node, and then uses another HTTP Request n8n node (🔍 Check Processing Status1) to query the container's status.


5. Status Check & Retry: The ✅ Is Container Ready? n8n node checks if the statuscode equals FINISHED. If the container is still processing, the workflow is routed back to the ⏰ Retry Wait Loop n8n node, which pauses and then re-checks the status. This guarantees a reliable publication only when the content is ready.


6. Final Publishing: Once verified as FINISHED, the 🔀 HTTP vs FB API Router n8n node selects the final publication method (either the generic HTTP Request n8n node or the Facebook SDK n8n node) to call the /mediapublish endpoint, making the content live on Instagram.

To use this n8n workflow template, follow these steps:

1. Import: Copy the provided JSON data and paste it into your n8n instance via the 'Import from JSON' option.


2. Credentials Setup: This n8n workflow requires two types of credentials for the Facebook Graph API:

1. Configure Settings: Open the ⚙️ Configure Post Settings n8n node and replace the placeholder values (e.g., node ID, imageurl, videourl, and the desired post_type) with your actual data.


2. Test: Run the n8n workflow manually using the 🚀 Manual Trigger to test the content flow.

This complex n8n workflow utilizes numerous specialized and flow control nodes:

🚀 Manual Trigger - Start Workflow (n8n trigger): Initiates the execution for testing purposes.
⚙️ Configure Post Settings (Set n8n node): Acts as the input source, setting all dynamic parameters (IG ID, URL, Caption, posttype).
🔀 Smart Content Router (Switch n8n node): Essential flow control n8n node that directs the data based on the posttype variable to the appropriate container creation endpoints.
Container HTTP/FB Nodes (HTTP Request / Facebook Graph API n8n node): Multiple instances of these nodes (Container HTTP Image, Container FB Reels, etc.) are used to call the Graph API's /media endpoint to create the initial media container.
Container Carousel Image 1 & 2 (HTTP Request n8n node): Specialized n8n nodes necessary to create the child containers for a multi-image carousel post before the parent container can be assembled.
🔍 Check Processing Status1 (HTTP Request n8n node): Polls the Graph API using the container ID and the fields=statuscode query to check if the media processing is complete.
✅ Is Container Ready? (If n8n node): Determines if the statuscode is FINISHED. Crucial for controlling the polling loop.
⏰ Initial Processing Wait / ⏰ Retry Wait Loop (Wait n8n node): Implements time delays necessary for asynchronous Graph API operations, preventing overwhelming the API and ensuring the polling logic functions correctly.

• 📤 Publish via HTTP API / 📤 Publish via Facebook SDK (HTTP Request / Facebook Graph API n8n node): These are the final action n8n nodes, calling the /mediapublish endpoint using the successful creationid.