Create Zendesk Ticket Node, doesn't have Requester field

Questions
, , ,
1

Hi, I have a workflow which turns Slack messages into tickets. This workflow contains formatters to pull information from the message like email, phone number, etc. In the last step, I need it to create a ticket using the information extracted from the previous node.

The step before the ticket creation is Zendesk user creation, it creates a user for unique email addresses, and updates if they are already a user. This allows me to have a user ID available in creating a ticket.

But on the last step, “create a ticket” in Zendesk node, it doesn’t have the fields I need to set the requester, or the user of the ticket. It also doesn’t have a way to make the first comment private.

I’m not good at coding to make my own HTTP request so I’m relying on the available features in the nodes. If I really need to do it, can someone explain it in a way that’s easy to understand for begginners.

Our company relied on the native integration of zendesk and Zapier, so we are still unsure if using this N8N workflow would be effective given this issue.

2

Looking at the Zendesk node documentation, you can set the requester using the “Additional Fields” section in the Create Ticket operation. Add a field called `requester_id` and use the user ID from your previous Zendesk user creation step. For private comments, you can add `comment` as an additional field with `public: false` in the comment object.

If you need more control, here’s a simple HTTP Request approach:

• Use HTTP Request node with POST method to `https://[your-subdomain].zendesk.com/api/v2/tickets.json`

• Set authentication to use your Zendesk credentials

• In the body, structure it like: `{“ticket”: {“requester_id”: {{$node[“Zendesk_User”].json[“id”]}}, “subject”: “Your subject”, “comment”: {“body”: “Comment text”, “public”: false}}}`

Check out the [n8nworkflow.net](Create a ticket in Zendesk - N8N Workflow Directory) example workflow for reference on customizing Zendesk ticket creation with additional fields.

3

@Nico.b did this work?

4

I tried it out last night, and the custom field ‘requester_id’ isn’t supported, as well as ‘comment’.

I managed to do it by writing JSON parameters directly, still on the Zendesk node and this is how it looked like:

{
“subject”: “{{ $(‘Code in JavaScript’).item.json.storeName }}”,
“requester_id”: {{ $json.id }},
“submitter_id”: ,
“group_id”: ,
“assignee_id”: ,
“tags”: [“created_from_n8n”],
“status”: “solved”,
“comment”: {
“body”: “TEST BODY”,
“public”: false
},
“custom_fields”: [
{
“id”: 0000000,
“value”: “{{ $(‘Code in JavaScript’).item.json.firstName }} {{ $(‘Code in JavaScript’).item.json.lastName }}”
},
{
“id”: 0000000,
“value”: “TEST VALUE”
},
{
“id”: 0000000,
“value”: “TEST VALUE”
},
{
“id”: 0000000,
“value”: “TEST Value”
},
{
“id”: 0000000,
“value”: “TEST Value”
},
{
“id”: 0000000,
“value”: “TEST Value”
}
]
}

This one worked seamlessly. Almost everything I needed on the ticket were filled out.