Trello node fails with 403 on GET operations

[faevourite]

Bug Description

All "get" operations like getting a board fail with a 403 error. It's likely due to this deprecation notice on the Trello API dev changelog. It suggests that the Trello node is sending a payload with GET requests.

Also, see this community post.

Part of the error:

ERROR: Forbidden - perhaps check your credentials?
403 - "\n\nERROR: The request could not be satisfied\n\n403 ERROR\nThe request could not be satisfied.\n\nBad request.\nWe can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n
\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n
\n\n\nGenerated by cloudfront (CloudFront)

To Reproduce

1. Add a Trello node with a get, such as "Get Board"
2. Provide a board id
3. Test the step

Expected behavior

Should succeed. Now returns a 403 matching the one from the linked deprecation notice.

Operating System

Ubuntu via official Docker

n8n Version

1.27.2

Node.js Version

18.19.0

Database

SQLite (default)

Execution mode

main (default)

[Joffcom]

Hey @faevourite,

It looks like someone has popped in a PR to fix this one so as soon as the CLA is signed by the user we will be able to get it merged in for a future release.

[janober]

Fix got released with [email protected]