Zendesk Make integrationAutomate Zendesk with Make.

List Tickets brings the queue into the scenario, one bundle per ticket, archived and soft deleted ones left aside. Each bundle costs an operation, and an operation is one run of one module on one item.

Search Tickets takes the criteria you give it and returns what matches, which can be zero, one or several tickets.

Soft deleted tickets vanish from the usual lists, and this module is the one that shows them again inside a scenario.

Aim Get a Ticket at a single request and it returns that request as it stands, ready to be read by the module that follows.

Create a Ticket opens a request in Zendesk from whatever the scenario is carrying, a failed order, a form answer, a line in a file.

Update a Ticket writes on a request that already exists, and the same call can add a comment while it is at it.

When the same person writes twice about the same thing, Merge Tickets folds the duplicates into a single request and keeps the conversation in one place.

Soft Delete a Ticket takes a request out of the working lists without wiping it, which leaves a way back through List Soft Deleted Tickets.

Permanently Delete a Ticket removes the request for good. Nothing lists it afterwards, not even the module built for soft deleted ones.

Upload Attachments sends files to Zendesk and keeps them waiting for the ticket that will carry them.

The whole comment history of one ticket comes back through this module, each comment as its own bundle.

Create a Ticket Comment posts a message on an existing ticket, which is how a scenario speaks to the customer or leaves a note for the agent.

Custom fields built as drop-downs carry a list of options, and this module reads that list into your scenario.

This one adds a choice to a drop-down field, or changes it when it is already there, with nobody opening the Zendesk settings.

Taking a choice off a drop-down field is the whole job of this module, and it does only that.

Side conversations are the side threads attached to a ticket, and this module lists the ones a given ticket holds.

Each side thread keeps a record of what happened in it, and this module reads those records for one conversation on one ticket.

Starting a new side thread on a ticket is this module's whole job, which lets a scenario bring a third party into a case without mixing them into the customer conversation.

Get a Side Conversation returns one thread, identified by the ticket it hangs from, with its current details.

The state or the subject of a side thread can be changed from a scenario, and this is the module that does it.

Replying inside an existing side thread happens here, so the exchange stays in one place instead of starting over somewhere else.

Every organization in the account comes back through List Organizations, one company per bundle.

Search Organizations looks for the companies matching your criteria and hands back what it finds, which may be nothing at all.

One company, read in full: Get an Organization returns the record your scenario points at. It reads and never writes, so it is safe to drop anywhere in a flow.

Create or Update an Organization writes the company into Zendesk, creating it when it is missing and refreshing it when it is already there.

Update an Organization touches companies that already exist and nothing else, which makes it the safer pick when a creation by mistake would be a problem.

Deleting a company from the desk is what this module does, and the scenario around it carries the responsibility.

List Groups returns the teams of your Zendesk account, one group per bundle.

Details of a single team come back with Get a Group, when the scenario already knows which one it means. Short module, handy glue.

Create a Group opens a new team on the desk from a scenario, without a trip through the admin screens.

An existing team can be modified here, which is often enough to keep naming consistent on a desk that keeps growing.

Delete a Group takes a team off the desk. Short module, long consequences for the people who were working in it.

List Users hands over the people Zendesk knows, and the list can be narrowed to one group or to one organization.

Looking somebody up by your own criteria is the job of Search Users, which returns zero, one or several people.

Get a User returns one person, the one your scenario points at, with what Zendesk holds about them.

This module goes past the identity card and returns what is attached to a person: their tickets, their topics, their subscriptions.

Create or Update a User puts a person into Zendesk, or refreshes the record when that person is already known to the desk.

Update a User changes somebody who already exists, and nothing else: no record appears by accident with this one.

Delete a User removes a person from Zendesk. Run it knowingly, because no scenario puts the record back afterwards.

Search Anything casts a wider net than the other search modules: tickets, users, organizations, whatever matches the query comes back.

A tag costs nothing and makes a record easy to find later. Add, Replace or Remove Tags puts them on a ticket, a user or an organization from inside the scenario. Adding keeps what is there, replacing swaps the whole set for what you send.

When none of the 55 modules covers what you need, Make an API Call sends a request you write yourself to the Zendesk API, over the connection you already created, and passes the answer to the next module.