Keep your support team in sync. New Zendesk tickets start a Slack thread so everyone can discuss and act fast. Perfect for teams that manage tickets in Zendesk but coordinate work in Slack.

A webhook fires when a ticket is created. The flow fetches the ticket, looks for a custom field that stores a Slack thread ID, and takes the right path. If the field has an ID, it posts the new comment to that existing Slack thread. If not, it creates a new message in a set Slack channel using the ticket subject and then writes the Slack thread timestamp back to the ticket field. This links the ticket and the Slack thread for all future updates.

You will need a Zendesk API token, a Slack OAuth connection, and a custom field in Zendesk to hold the Slack thread ID. Expect less copy and paste, fewer duplicate Slack posts, and all updates in one place. Many teams cut manual posting time by about 90 percent and make handoffs smoother. Set your Slack channel in the Configure node and update the custom field ID in the Code and Update nodes. Activate and test with a sample ticket to confirm the field updates and replies land in the same Slack thread.

• Webhook trigger listens for new Zendesk tickets and starts the flow
• Gets full ticket details to use the subject and latest comment
• Custom field check stores and reads the Slack thread ID from Zendesk
• Conditional routing sends updates to an existing thread or creates a new one
• Creates a Slack thread in a chosen channel using the ticket subject
• Posts new comments into the same Slack thread using thread timestamp
• Writes the Slack thread timestamp back to the Zendesk custom field
• Central channel selection using a Configure node for easy changes

• Reduce manual cross posting from 5 minutes to under 30 seconds per ticket
• Eliminate up to 90% of duplicate Slack posts for the same ticket
• Improve update accuracy by posting directly from the source system
• Handle higher ticket volume without adding extra steps for agents
• Connect Zendesk and Slack so teams work from one shared thread

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Zendesk and Slack. See the Tools Required section above for links to create accounts with these services.
3. In the n8n editor, open the On new Zendesk ticket node and copy the Production URL. Keep this URL ready for your Zendesk webhook or trigger.
4. Set up Zendesk credentials: double click the Get ticket node, open the 'Credential to connect with' dropdown, click 'Create new credential', then follow the on screen instructions. In Zendesk, create an API token in Admin Center and paste your subdomain, email, and API token into n8n.
5. Authorize Slack: double click the Create thread node, choose 'Create new credential' for Slack OAuth2, and complete the authorization flow. Repeat for the Create reply on existing thread node if needed.
6. Create or confirm a Zendesk custom field to store the Slack thread ID. Copy its field ID from Zendesk. In n8n, update this ID in the Code node constant and in the Update ticket node so both point to your field.
7. Set your Slack channel: open the Configure node and change the Slack channel value to the target channel, such as #zendesk-updates.
8. Configure the Zendesk webhook or trigger: in Zendesk Admin Center, create a trigger that runs on ticket creation and sends a POST request to the n8n webhook URL. Include ticket ID and latest comment in the payload.
9. Activate the workflow in n8n. Create a test ticket in Zendesk and confirm a new Slack message appears in the chosen channel. Check that the Zendesk custom field now holds the Slack thread timestamp.
10. Troubleshoot: if no Slack post appears, verify Slack and Zendesk credentials. If messages do not thread, confirm the custom field ID matches in both the Code and Update ticket nodes. If duplicates appear, ensure the trigger only fires on create and that the field is being updated correctly.