Facebook Node (to Instagram) OAuth invalid request invalid parameter

[mailfraud]

Describe the problem/error/question

I am using a Facebook Node to post videos on Instagram. That worked, but now throws the message

What is the error message (if any)?

www-authenticate:OAuth "Facebook Platform" "invalid_request" "Invalid parameter"

It is strange because the forgoing node to create the story container works with the same credentials. Does anybody know if that is a bug?

Please share your workflow

Share the output returned by the last node

[
{
“statusCode”: 400,
“headers”: {
“debug-link”: “Redirecting...”,
“error-mid”: “478ac356383b44ed3122ddb34409bd17”,
“vary”: “Origin, Accept-Encoding”,
“x-fb-aed”: “756”,
“x-business-use-case-usage”: “{"280249xxxxxxx":[{"type":"instagram","call_count":1,"total_cputime":1,"total_time":1,"estimated_time_to_regain_access":0}],"1784146567xxxxxxx":[{"type":"instagram","call_count":1,"total_cputime":1,"total_time":1,"estimated_time_to_regain_access":0}]}”,
“content-type”: “application/json”,
“www-authenticate”: “OAuth "Facebook Platform" "invalid_request" "Invalid parameter"”,
“access-control-allow-origin”: “*”,
“facebook-api-version”: “v24.0”,
“strict-transport-security”: “max-age=15552000; preload”,
“pragma”: “no-cache”,
“cache-control”: “no-store”,
“expires”: “Sat, 01 Jan 2000 00:00:00 GMT”,
“x-fb-request-id”: “AQBT2AWFpL3fRu2ch8IP-Y6”,
“x-fb-trace-id”: “EKy5j6g04rL”,
“x-fb-rev”: “1034114706”,
“x-fb-debug”: “oeapyKYaYzU69en99pvLFx82AIMNkHpmQfcvpNQjst+nadk4C1ZfGEO8uVEdFgvBZlpc43OdGZgr2PTDZ2Otyw==”,
“date”: “Thu, 26 Feb 2026 12:50:55 GMT”,
“proxy-status”: “http_request_error; e_fb_vipaddr="AcOFNr4J-mnBlZA9m-fZE3WqpwnGGRAoLpJyXZqf-swQsMUrF7r7WCnsZGF16qwVMezo5cLC3MMylq7uv2sYBqdI1nmCTpi8jYNUaQ"; e_clientaddr="AcO0RbO4ltq0NfQRE-_0TYwBclBSnAkLREViKGsuSKVadyz9EqB6gi9AXdOy-S81kANAMn-lqGuDPkWmEfIw7Ey7s6xh-sc6z6HZUoCMQrc_xJ8eSg"; e_upip="AcPj8fPDEl3jZ9_GxITjjxY2KthxI5tDr4o46_yOfmhUzM-mC2SR07XxfyuVW4JmcZ57QDsVlaNp0tjaFBlEU5GNA9yhi82-rZywRTGjlZI"; e_fb_zone="AcMBnuinJouM_MoEB-K7bEj6A9Ic6SOWc6j2RHg8ng9gOS9A0hAjzZeLE6qRIeGU"; e_fb_twtaskhandle="AcMwgltyP8zNwvs08sWAFE7jKlIl-GULOPfwDtu6ovVPzXhH9fBqkMBixjXVwcJe7KeELF64GNf89afv5AskFjWJ5G-5B2GsNwIGDDj2NopHc4M"; e_proxy="AcPl9CBFe9AYggDljbpOB6IYyY_uD5sKnn06bLJzr96_nmTjUfcT-s1uptI9Apt4MkpFADHGWQ95WfZULhDb", http_request_error; e_fb_vipaddr="AcNvoOxJDstBuagIHEafixJQqqKs_qesc-C-8c0Bt2W-_t1nSqT_Qgu5Mk6Y240i3qsbd_dBpg"; e_clientaddr="AcPUauLnYL275A5hgE32NRw3iibMiu6q6XeRzNVwOOOiDHHBGtIFBg5XgvagbYDYDQY8jF7cuF6iFfzHLw"; e_upip="AcPhYHj16t-7QdeFeKA_GGMltYmGD50zybibLR9Dsv8L1W9HawwmKtMSwVPYTh0ihbsCONEMki2g9XQ-ieSZCVdBZ2Vh8lkpm1T8Nw"; e_fb_zone="AcMnGNQlSka0Z10iGezZfuG9YWW_3HHiPmFOSYjALipe–yb_JKi3gJcwyZNxQ"; e_fb_twtaskhandle="AcPalq5L5z1VrDbRlQ-xTf8NB52RnOTjZO7g6EZQNm3xWjfIW3Bgue1r_3NCzPHTVxNFD4UvAFEWeIVnIEYL9NGyEnLwteAYi1oc"; e_proxy="AcOCfepEa8-7exGAvcm2NB8MQdjk0kqiZ_J8i2KPNKQdySkPnVMhx77Cy4KUALcSQpeZdXmJ2GUhDmY"”,
“connection”: “close”,
“content-length”: “276”
}
}
]

Information on your n8n setup

• n8n version: 2.9.4
• Database (default: SQLite): yes
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app): podman
• Operating system: macOS

[A_A4]

Hi @mailfraud

the issue is in the hostUrl setting of your final node (“ Publish to Instagram”).

you currently have it set to graph-video.facebook.com. change it to graph.facebook.com.

graph-video.facebook.com is only used for uploading raw video files directly to standard facebook pages.instagram’s two-step video process (creating the container, then publishing) requires the standard graph.facebook.com endpoint for both steps.sending the publish command to the video-specific server triggers that “invalid parameter” error because the server doesn’t recognize the command.

just swap that url and your story will publish.

[mailfraud]

Thank for your tipp! I tried (also multiple combinations like expression etc.). The problem persists, however. Couldn’t there be a bug? I cannot roll back unfortunately, but this workflow did work.

[A_A4]

@mailfraud
when n8n pauses at a Wait node, it saves the workflow state to your database. when it wakes up 30 seconds later, it sometimes struggles to recall data from nodes that ran way earlier in the flow.

your final node relies on this expression: {{ $('📤 Create Story Container').first().json.id }}

if n8n drops that context after waking up, it sends a completely blank creation_id to meta. meta sees the missing ID and instantly rejects the request with an “invalid parameter” error.

how to check: open the failed execution log and look at the exact input the final node tried to send. if the creation_id field is empty, there’s your bug.

[mailfraud]

@A_A4 thanks for another hint! But that does not seem to be it. ID is correct. I realised though, that the FB node says there is an issue with API version 24. When I try 23, however, Facebook API automatically changes to 24 again. Very strange.

[tamy.santos]

Hi @mailfraud !
I would recommend checking the v24 changelog for the Instagram publish endpoint and verifying that all parameters you send are still supported.

[mailfraud]

@tamy.santos thanks for your input! Did that - looks fine, nothing special. I do not understand why n8n warns that v24 is not supported. It worked before for several weeks before updating.

[A_A4]

@mailfraud
n8n’s built-in facebook node doesn’t fully support meta’s new v24.0 api yet. but as your logs show, meta is aggressively forcing all v23.0 requests to upgrade to v24.0 anyway.

you can ditch the facebook node now for that final step and use a standard HTTP Request node instead.

set the new node up like this:

• Method: POST
• URL: ={{ 'https://graph.facebook.com/v24.0/' + $('🎯 Prepare Video Data').item.json['instagram_business_id'] + '/media_publish' }}
• Authentication: Predefined Credential Type → Facebook Graph API
• Send Query Parameters: toggled on
• Query Parameters: Name: creation_id, Value: ={{ $('📤 Create Story Container').first().json.id }}

[mailfraud]

It just started working again - so it was a Facebook issue. It also makes no difference if I use the graph or graph-video address for me.

Thanks for your input and help, it is much appreciated!