Zammad ticket creation misses to field and fails

[hachi]

Describe the problem/error/question

Create a ticket via Zammad node

What is the error message (if any)?

email to is missing.

The problem is the missing to in the body.

Anyway to fix this either in the node or locally?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

{
  "errorMessage": "Your request is invalid or could not be processed by the service",
  "errorDescription": "Sending an email without a valid recipient is not possible.",
  "errorDetails": {
    "rawErrorMessage": [
      "422 - {\"error\":\"Sending an email without a valid recipient is not possible.\",\"error_human\":\"Sending an email without a valid recipient is not possible.\"}"
    ],
    "httpCode": "422"
  },
  "n8nDetails": {
    "nodeName": "Zammad",
    "nodeType": "n8n-nodes-base.zammad",
    "nodeVersion": 1,
    "resource": "ticket",
    "operation": "create",
    "time": "17/03/2025, 14:59:43",
    "n8nVersion": "1.81.4 (Self Hosted)",
    "binaryDataMode": "default",
    "stackTrace": [
      "NodeApiError: Your request is invalid or could not be processed by the service",
      "    at ExecuteContext.zammadApiRequest (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/nodes/Zammad/GenericFunctions.ts:79:9)",
      "    at processTicksAndRejections (node:internal/process/task_queues:95:5)",
      "    at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/nodes/Zammad/Zammad.node.ts:686:22)",
      "    at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1123:8)",
      "    at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1470:27",
      "    at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:2029:11"
    ]
  }
}

Information on your n8n setup

• n8n version: 1.81.4
• Database (default: SQLite):
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app): self-hosted via npm
• Operating system: Ubuntu

API

Running the API command via curl requires the to in the json field - which is apparently missing in n8n node.

-H “Authorization: Token token=dd”
-H “Content-Type: application/json”
-d ‘{
“title”: “New Ticket Title”,
“group”: “wicked.design”,
“customer”: “[email protected]”,
“article”: {
“subject”: “Subject of the ticket”,
“body”: “This is the body of the ticket.”,
“type”: “email”,
“internal”: false,
“to”: “[email protected]”,
“sender”: “Customer”
}
}’
“http://helpdesk.domain.my/api/v1/tickets”

[Dandy_Dow]

Hey Hachi,

Yep — you’re right on the money. The issue is that when the article.type is set to "email", the Zammad API expects a to field inside the article object, otherwise it throws that 422 error about missing recipients.

From what it looks like, the current Zammad node in n8n doesn’t expose the to field as an input when creating a ticket, so it just gets skipped in the payload — even though it’s required for email-type articles.

Quick workaround:

Until this gets patched on the n8n side, you can bypass the built-in Zammad node and go with an HTTP Request node like this:

• Method: POST
• URL: http://helpdesk.domain.my/api/v1/tickets
• Headers:
  • Authorization: Token token=your_token_here
  • Content-Type: application/json
• Body (RAW / JSON):

{
  "title": "New Ticket Title",
  "group": "wicked.design",
  "customer": "[email protected]",
  "article": {
    "subject": "Subject of the ticket",
    "body": "This is the body of the ticket.",
    "type": "email",
    "internal": false,
    "to": "[email protected]",
    "sender": "Customer"
  }
}

This gives you full control over the payload and ensures to is included.

If you’re using this often, it might even be worth creating a small custom node or submitting a PR to add support for the to field in the official Zammad node.

Let me know if you need help wiring up the HTTP node version — happy to drop an example into a workflow!

Dandy