GET operations in Trello node fail

Describe the problem/error/question

All my Trello nodes that use GET Operations (e. g. Card → Get, Board → Get) return errors since Feb 22. I have observed this behavior partially a few days before as well.

Since my credentials are ok and other operations work as expected I guess this is related to a recent change in the Trello API which doesn’t allow body content for GET requests anymore. Source

When I call the Trello API manually with at HTTP Request node (omitting the body) the GET operations work as expected.

What is the error message (if any)?

403 - ERROR: The request could not be satisfied. We 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.

Information on your n8n setup

  • n8n version: 1.27.3
  • Database (default: SQLite): PostgreSQL
  • n8n EXECUTIONS_PROCESS setting (default: own, main): default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Ubuntu

I think this is due to this:

EDIT - I didn’t see your link in your original post! I will keep the notice below for easy access.

20 February 2024

DEPRECATION NOTICE Trello API will no longer accept GET request with data in body

REST API - Trello

Trello’s API will no longer permit supplying a body with a GET request. Previous behavior in our API ignored the payloads provided with GET requests but these requests will now be blocked with a 403 response from our content delivery network.

To resolve issues resulting from this change ensure all GET requests to Trello’s API are sent without a payload.

I am looking at temporarily converting them to HTTP Request Nodes as it is pretty vital for us.

1 Like

Yeah, I had to rewrite about 20 workflows this morning as well. At least there is a workaround.

Someone kindly put in a PR for this which has been merged we will just need to wait for the next release to get the fix out there.

thats a crazy thing to just instantly deprecate without notice

1 Like

Hey! How fast will we get a new release with this fix? I want to understand if I should create docker-image by myself and use it on server or new release is coming soon.

Hey @DanielGots,

Welcome to the community :raised_hands:

If it is urgent making an image will be the quickest option otherwise we may be doing a release tomorrow depending on what else pops up overnight.

1 Like

I really hope there’s a new release coming today :slight_smile:

New version [email protected] got released which includes the GitHub PR 8715.


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