Hi @Talha_Saeed Welcome!
It can be due to the limitation of built in n8n nodes supporting a specific set of operations only, and as you have discovered the solution for yourself is that to use HTTP request node instead, and this would be a good feature request if the user base is big.
we ran into the same thing with zammad, the node just doesnt support all the custom fields the api exposes. the http request workaround works but you’ll need to manually map everything — worth documenting what fields you need first
but i want to use Zammad node direclty as it seems easier and simple. is there any possible way ?
there is no way that Zammad node can send additional fields ?
@Talha_Saeed if that built in node does not support the operation you want, there is nothing you can do other then using HTTP node.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.