I’m trying to integrate the FAL Veo3 API into an n8n cloud workflow

[jk14ore]

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

[Joffcom]

Hey @jk14ore,

Thank you for reaching out! We’ve received your issue and are looking into it. To help us track this internally, we’ve created a Linear ticket with the reference: "GHC-5008".

We’ll keep you updated as we make progress, but if you have any additional details or context to share, feel free to add them here - it’s always helpful!

Thanks for your patience and for bringing this to our attention.

---

For INTERNAL use only: GHC-5008