stopped working on any version beyond n8n v1.46.0

[anantanandgupta]

Hi @LucasSovre, are you planning to maintain this project in future. we have updated to version 1.46.0 and it stopped working. i guess the n8n APIs are changed from this version and the module you have is not able to work with the same. older versions it works fine. all the requests where the POST/PUT methods are getting called are failing as it is not able to parse the body as per my understanding.

[LucasSovre]

Hi @anantanandgupt, i have seen your issue and topic on n8n community forum (https://community.n8n.io/t/community-node-is-no-longer-visible/46665/9)

indeed, I am really busy at work this days... but I will be back in September, if you want I can give you rights to approve merge request, then you will can create release and the GitHub action will take care for pushing new versions to npm registry

[anantanandgupta]

thanks @LucasSovre ... i will help you maintain this repository.

[anantanandgupta]

I tried to figure out the reason why it is not working on latest versions of n8n . It seems it is something to do with the node defaults. Will investigate more and keep all posted on the findings. It is unfortunate that n8n team is not giving any justifications rather and we don’t have any optimal debugging mechanism where we can test debug the community nodes against different versions of n8n.

[LucasSovre]

Hi @anantanandgupta, i will do complete rework of the node in September, using the programmatic node style. I wish it will be easier to maintain and be more compatible with n8n.

[anantanandgupta]

Hi @anantanandgupta, i will do complete rework of the node in September, using the programmatic node style. I wish it will be easier to maintain and be more compatible with n8n.

No point in writing the complex node style. Just need to figure out what causing the post body to become empty in any operation which is calling the post apis.

[LucasSovre]

Did you tried to spy the network requests using a tool like wireshark to debug it ? I wrote a tutorial about it while creating this node : https://www.entrecompetents.fr/blog/en/dev/debug-api-wireshark/ Le sam. 3 août 2024 à 13:55, Anant Anand Gputa ***@***.***(mailto:Le sam. 3 août 2024 à 13:55, Anant Anand Gputa <<a href=)> a écrit :

…

> Hi ***@***.***(https://github.com/anantanandgupta), i will do complete rework of the node in September, using the programmatic node style. I wish it will be easier to maintain and be more compatible with n8n. No point in writing the complex node style. Just need to figure out what causing the post body to become empty. In any node which is calling the post apis. — Reply to this email directly, [view it on GitHub](#10 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ASPTSGTTPSXBTSQHHKIE3H3ZPTALRAVCNFSM6AAAAABKYU3UYSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRWGY4DQNBWG4). You are receiving this because you were mentioned.Message ID: ***@***.***>

[anantanandgupta]

Yes ... Thats how I know that the request body is becoming empty before it is sent. There is somewhere the code overwriting the body after the operation is evaluated. There seems to be a node default configuration which when loaded, overwriting the evaluated operation. Like while iterating the operations and building the request configuration it builds the proper body, but by the end once the iteration is completed, it is set to undefined for body field of the request configuration.

[AlejandroAkbal]

Any chance this node starts working again? :(