Zammad's name changed to a customer's name on my server.

Technical assistance
1

Infos:

I am running a self-hosted Zammad with n8n creating and updating new tickets.

  • Used Zammad version: 6.5.1
  • Used Zammad installation type: docker-compose
  • Operating system: ubuntu
  • Browser + version: firefox- 148.0

Expected behavior:

  • When new tickets come in, I would expect it to say Zammad created article for…

Actual behavior:

  • Currently it says A Specific Customer’s Name created article for…

Steps to reproduce the behavior:

  • I do not know I believe I was trying to rename my first customer at the very beginning and now it kept that name as Zammad’s
2

Does n8n use a specific zammad user ID to create tickets? I’m not sure if you provided enough info to fully figure out what’s going on, but it sounds as if n8n is creating the tickets as the customer via the zammad API. I know the API has flags that allow a ticket created via the API to be created on behalf of another user (see here). Perhaps it would need to create the ticket as your service account user instead for you to get the desired effect.

3

So what I have figured out, is from n8n using the create ticket, it uses three options for the sender: System, Customer, and Agent. if I select customer, it will select my first customer’s name, not the actual customer. If I select System or agent it uses the agents name. and I am using the official zammad n8n nodes. I am also having issues with the article type for email saying you can email without a recipient but I have an email in the reply to box for the create ticket node.

But when system or agent is selected, it has the agent as this:
[ William N*** created article for Bug Report 33 minutes ago](ticket link) for the activity stream but the current owner of these are my first customer not a blank owner. Those that are sent with customer looks like this on the activity stream: [ Timothy N**** updated ticket Report a Bug 33 minutes ago ](ticket link) and the owner of the ticket is me.

4

Maybe some screen shots of configuration with sensitive info blanked out could help. You posted a direct link to your instance. So is William Whoever a person user on your instance that n8n is logging in as? Cause I’d assume that the actions taken under agent or system would indeed use that user. You probably should make a dedicated user for n8n activities.

5

I noticed that the nodes are using outdated token permissions. one is ticket.customer, which I bet was used to create a ticket on the user’s behalf.