Workflow fails with a 405 Method Not Allowed error, even though the method is set to GET

Describe the problem/error/question

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"
  }
}

Looking at the documentation of FAL you might be using the wrong URL indeed. I understand the process to be as follows:

1 Like

Hi thanks for your response. are you saying i should update my call status url endpoint to https://queue.fal.run/fal-ai/veo3/requests/{{$json.request_id}}/status ? if thats the case i get a seperat error: Invalid URL: https://queue.fal.run/fal-ai/veo3/requests/2ed27666-7b51-47ab-9171-32706ce845f8/status. URL must start with “http” or “https”.

ive fixed the error above im saying this error. {
“errorMessage”: “Authorization failed - please check your credentials”,
“errorDescription”: “Cannot access application ‘fal-ai/veo3’. Authentication is required to access this application.”,
“errorDetails”: {
“rawErrorMessage”: [
“401 - “{\“detail\”: \“Cannot access application ‘fal-ai/veo3’. Authentication is required to access this application.\”}””
],
“httpCode”: “401”
},
“n8nDetails”: {
“nodeName”: “CheckStatus (HTTP Request)”,
“nodeType”: “n8n-nodes-base.httpRequest”,
“nodeVersion”: 4.2,
“itemIndex”: 0,
“time”: “10/14/2025, 10:06:28 PM”,
“n8nVersion”: “1.114.4 (Cloud)”,
“binaryDataMode”: “filesystem”,
“stackTrace”: [
“NodeApiError: Authorization failed - please check your credentials”,
" at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@[email protected]_asn1.js@5_afd197edb2c1f848eae21a96a97fab23/node_modules/n8n-nodes-base/nodes/HttpRequest/V3/HttpRequestV3.node.ts:847:16)“,
" at processTicksAndRejections (node:internal/process/task_queues:105:5)”,
" at WorkflowExecute.executeNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_08b575bec2313d5d8a4cc75358971443/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1091:8)“,
" at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_08b575bec2313d5d8a4cc75358971443/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1272:11)”,
" at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_08b575bec2313d5d8a4cc75358971443/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1673:27",
" at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_08b575bec2313d5d8a4cc75358971443/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:2287:11"
]
}
}

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.

1 Like

I fix this issues but now faced with this error: ive fixed the error above im saying this error. {
“errorMessage”: “Authorization failed - please check your credentials”,
“errorDescription”: “Cannot access application ‘fal-ai/veo3’. Authentication is required to access this application.”,
“errorDetails”: {
“rawErrorMessage”: [
“401 - “{\“detail\”: \“Cannot access application ‘fal-ai/veo3’. Authentication is required to access this application.\”}””
],
“httpCode”: “401”
},
“n8nDetails”: {
“nodeName”: “CheckStatus (HTTP Request)”,
“nodeType”: “n8n-nodes-base.httpRequest”,
“nodeVersion”: 4.2,
“itemIndex”: 0,
“time”: “10/14/2025, 10:06:28 PM”,
“n8nVersion”: “1.114.4 (Cloud)”,
“binaryDataMode”: “filesystem”,
“stackTrace”: [
“NodeApiError: Authorization failed - please check your credentials”,
" at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@[email protected]_asn1.js@5_afd197edb2c1f848eae21a96a97fab23/node_modules/n8n-nodes-base/nodes/HttpRequest/V3/HttpRequestV3.node.ts:847:16)“,
" at processTicksAndRejections (node:internal/process/task_queues:105:5)”,
" at WorkflowExecute.executeNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_08b575bec2313d5d8a4cc75358971443/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1091:8)“,
" at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_08b575bec2313d5d8a4cc75358971443/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1272:11)”,
" at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_08b575bec2313d5d8a4cc75358971443/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1673:27",
" at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_08b575bec2313d5d8a4cc75358971443/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:2287:11"
]
}
}

It looks like you’re not sending the api key at all or not send it in the required way. It’s hard to tell thought without seeing the workflow.

this is my current work flow + the error i encounter within my get node

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?

{{ $json.response_url }}

That should do the trick.

i tried the above endpoint and this is what i get. its driving me mad! i cant see whats wrong here.

heres my check status call - looks ok and works fine

We’ll get there, no worries :wink:

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:

  1. Try the request in a different tool than n8n, just to see if you get the same error
  • the easiest is to download https://www.postman.com/ and try to do the request from there
  • you can also try to execute this command which will do the request as well (don’t forget to replace “YOUR-KEY” with your API key)

a) With Mac

Sorry I have trouble sending the full message, I get a strange error from the forum…

b) would be if you use Windows, then you need to modify the command a bit

Option 2 would be to contact the support from FAL and tell them that you have trouble calling the “get result” endpoint.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.