However, when I try to fetch the tickets from Zammad, all I receive is some html source code (DOCTYPE…) and not the tickets.
So the problem seems to be that n8n doesn’t even have access to the Zammad tickets.
Since I’m completely new to n8n, can anyone please tell me what I could have possibly done wrong? I authenticate with my own user id, and didn’t change anything else on the Zammad integration.
Ensure to copy your n8n workflow and paste it in the code block, that is in between the pairs of triple backticks, which also could be achieved by clicking </> (preformatted text) in the editor and pasting in your workflow.
```
<your workflow>
```
Make sure that you’ve removed any sensitive information from your workflow and include dummy data or pinned data as much as you can!
Hmm, I tried out the Zammad node on my own instance and the node seems to work for me without an issue.
Could you make sure that your credentials are correctly set up and that your Zammad user account has the necessary permissions to access ticket data via the API? You should be able to check this from your Profile settings in your Zammad instance.
From what you described, if you’re getting an HTML source code as a node output, it might be that Zammad is returning an error page and it’ll be interesting to see the whole page content. You might be able to do this by selecting ‘Return All’ inside the node so the node returns the whole content instead of just the first 10 entries, or you can make a request to the Zammad tickets endpoint by entering https://<YOUR_BASE_URL>/api/v1/tickets in your browser if you’re logged in to your zammad instance already. That should give you a better idea of what the API is returning
The credentials are definitely ok - I have checked and tested authenticating with user / pw as well as with access token. Both times with the same result.
If I enter the https://<YOUR_BASE_URL>/api/v1/tickets link, I do see the tickets and statuses.
However, if I test the node in n8n, I still get the html output and no tickets. It seems that n8n receives a 403 error, according to the source code I receive back.
Do you have any idea, by any chance, how to narrow down the problem more?