I’m trying to integrate the FAL Veo3 API into an n8n cloud workflow to automatically generate videos.
The POST request (SendToVeo3) to https://queue.fal.run/fal-ai/veo3 works and returns both request_id and response_url correctly.
However, when using a subsequent HTTP Request (GET) node to poll the /response endpoint and retrieve the generated video, the workflow fails with a 405 Method Not Allowed error, even though the method is set to GET.
I’ve confirmed the URL format, authentication header, and method are correct, but the endpoint keeps returning a 405 or sometimes 422 depending on how the query string is formatted.
What is the error message (if any)?
{
“errorMessage”: “Method not allowed - please check you are using the right HTTP method”,
“errorDescription”: “405: Method Not Allowed”,
“errorDetails”: {
“rawErrorMessage”: [
“405 - “405: Method Not Allowed””
],
“httpCode”: “405”
},
“n8nDetails”: {
“nodeName”: “GET-only”,
“nodeType”: “n8n-nodes-base.httpRequest”,
“nodeVersion”: 4.2,
“itemIndex”: 0,
“time”: “10/13/2025, 10:09:10 PM”,
“n8nVersion”: “1.114.4 (Cloud)”,
“binaryDataMode”: “filesystem”
}
}
Please share your workflow/screenshots/recording
Summary
Node: SendToVeo3 → returns request_id + response_url
Node: BuildResponseURL1 → builds URL https://queue.fal.run/fal-ai/veo3/requests/{{$json.request_id}}/response?wait=6s
Node: GET-only → HTTP Request (method = GET) using that URL
Auth: Header Auth or manual Authorization header (Key <api_key>)
No body/query parameters
Screenshot examples attached:
GET-only node configuration
Execution output showing 405 error
## Share the output returned by the last node
{
"errorMessage": "Method not allowed - please check you are using the right HTTP method",
"errorDescription": "405: Method Not Allowed",
"errorDetails": {
"rawErrorMessage": [
"405 - \"405: Method Not Allowed\""
],
"httpCode": "405"
}
}
## Debug info
{
"errorMessage": "Method not allowed - please check you are using the right HTTP method",
"errorDescription": "405: Method Not Allowed",
"errorDetails": {
"rawErrorMessage": [
"405 - \"405: Method Not Allowed\""
],
"httpCode": "405"
}
}
That’s an odd error, as the url is obviously well structured. My approach for these kinds of task is usually to first get familiar with the API by building the requests in a tool like Postman. Once you‘ve figured out the right calls it‘s just a manner of transferring them to n8n.
That’s really helpful, thanks! The URL from the second screenshot looks pretty strange, you can just use the variable “response_url” from the previous step.
Can you please try to replace the URL field with this?
The “check status” call looks good, so let’s try to figure out why the “get results” call fails. I can’t see any issues with how you call it, and the error that you get doesn’t really make sense here: it says that you’re sending data in a wrong way in the “body”, which is a field that can not be present on a “GET” request that you are sending. It sounds more like a bug on the side of FAL.
I see two options:
Try the request in a different tool than n8n, just to see if you get the same error