CloudConvert Base Tool Doesn't Contain Credential Box

EDIT: IT WAS A VISUAL BUG WHERE IT SHOWED 2 NODES, 1 OFFICIAL AND 1 COMMUNITY, AFTER UNISINTALLING AND REINSTALLING AND UPDATING THE TAB, THERE IS ONLY THE COMMUNITY NODE, BUT JUST FYI, THERE IS A VISUAL BUG AS DESCRIBED.

i have the base official cloudconvert node in my workflow, but before i knew that there is an official node for cloudconvert, i installed their community node, then when i saw that there is an official one, i naturally deleted the community one.

when i entered both the trigger and the action nodes, both didnt have a credential box to connect the api (live nor sandbox for that matter)


after searching a bit, i figured i should check the community one if it has the same issue, turns out that it actually has a credentials box; problem only exists in the official one.

clicked on the official one with the community node installed, and surely enough, it also contains the credentials box now that i installed the community one.

tried deleting the community node, box disappeared again.

1 Like

Man can you tell me how did you install the community node for cloud convert.
I don’t seem to find it at all

1 Like

keywords:n8n-community-node-package CloudConvert - npm search maybe one of these

After you uninstall do u restart? there maybe conflict, I had weird behaviour of orginal node, after installing similar commuinty node, restart helped