Instagram publishing failure

[Local_Boost]

What is your goal?

To build a scalable and stable automated system (SaaS) using Make to publish content dynamically to a client’s Instagram Business Account (IBA). The system uses the two-step Graph API method (Container Creation followed by Media Publish). The Facebook publishing path is stable and fully functional.

What is the problem?

The system fails with a critical permissions error during the first step of the Instagram publishing protocol (Media Container Creation). This happens even with a valid Long-Lived Page Access Token, indicating a fundamental flaw in the external API call structure or permissions linkage.

Exact Error: We receive a 400 Bad Request / GraphMethodException with the message: Object with ID ‘[Page ID]’ does not exist, cannot be loaded due to missing permissions, or does not support this operation. This suggests the API is rejecting the token’s claim over the target page/account.

What have you tried so far?

Token Verification: The Access Token has been verified as a Long-Lived Page Access Token and includes all necessary permissions (e.g., pages_manage_posts, instagram_content_publish). The token is not expired.

Module Switch: The unstable one-step Create a photo post module was replaced with two raw HTTP: Make a request modules (Container Creation and Publish) to enforce the modern API protocol.

ID Mapping Audit: We confirmed that the error is not due to a blank ID. We have tested both possible URL structures for Container Creation:

Using the IBA ID in the URL path (…/{IBA ID}/media).

Using the Facebook Page ID in the URL path, with the IBA ID passed as a query parameter.

Both methods fail with the same permissions error, suggesting the token—though correct—is not authorized by Meta to act on that specific IBA ID via the current App settings.

App Setup: A new Meta App (LocalBoostPl-IG) was created, and the Website platform and Redirect URI were configured to eliminate external security blocks.

The unresolved issue remains a conflict between the token’s authorized entity (the FB Page ID) and the entity being addressed in the API call (the IBA ID) which the API is rejecting.

[Stoyan_Vatov]

Hey there,

can you show some screenshots of the module setup and the error message you are getting?

[Local_Boost]

Hello,

I have developed a scalable automation system (using Make, Airtable, and the HTTP module) to publish posts dynamically. I am facing persistent stability issues specifically with Instagram.

1. THE PROBLEM: TOKEN EXPIRY VS. INSTABILITY

My dilemma is that neither module provides a stable solution:

• Simple Module Failure: The native Instagram for Business: Create a photo post module works flawlessly, but the token it uses appears to be short-lived (I suspect it expires after only about an hour), forcing manual re-authorization constantly.

HTTP Failure: To solve the expiry issue, I attempted to implement the two-step HTTP protocol using my Long-Lived Page Access Token, but this method immediately results in various 400 Bad Request or (#200) Permissions error messages.

2. THE CURRENT HTTP SETUP (FORUM DEBUGGING)

I am unsure if the two-module HTTP setup I created is structurally correct, as I built it based on trial-and-error (and AI assistance).

• Module 1 (Creation): This module is intended to Upload the media and get the creation_id.

• Module 2 (Publication): This module is intended to Publish the post using that creation_id.

(Please refer to the attached screenshots of Module 1 and Module 2 for the exact URL and parameter configuration.)

3. THE ULTIMATE GOAL (LONG-LIVED TOKEN)

My objective is to permanently stabilize the Instagram publishing for my clients.

Question:

1. Architecture Validation: Is the two-step HTTP structure the correct way to handle Instagram publishing (given that the simple module is unstable)?

2. Token Implementation: How can I correctly map or ensure the Long-Lived Instagram Access Token is used in the module connection or the HTTP request, so that the token never expires (or lasts at least 3 months), resolving the root cause of the initial token expiry?

Thank you for any guidance on resolving this final, critical engineering block.

it’s frist module http make a request

and second module http

this error is when i use a instagram id page in second module

error when i use facebook id page