Zendesk Action Flows and Custom Agents in practice

What can Zendesk Action Flows and Custom Agents take off your team’s hands? In our webinar on 28 October 2026, we explored four service workflows. See how the features work together and what else you could use them for.

Leafworks: Zendesk Premier Partner
Zendesk Implementation Partner
Documents, an Action Flow and an AI agent connected in a service workflow

A customer enquiry often involves several small tasks before it can be resolved: looking up information, comparing details or transferring data to another system. This recurring work takes time away from conversations with customers.

Action Flows and Custom Agents can connect tasks that previously required someone to read a document and then continue working in another system. The examples show where fixed rules are enough and where AI in Zendesk can help. Our guide to Zendesk automation explains how these options fit into an existing setup.

Four service workflows from the webinar

In our joint webinar with Zendesk on 28 October 2026 (held in German, English subtitles available), we explored four applications. The returns example takes you through the full setup in Zendesk.

1 Process returns documents

A returns or cancellation document arrives as a PDF attached to a ticket. Its details are needed to handle the request. Gardena submitted this use case for the webinar. Tim Kopec built the workflow shown in Zendesk.

  1. PDF in the ticket

    A defined trigger starts the Action Flow, which controls the steps that follow.

  2. Details in the ticket

    The Custom Agent reads the document and extracts the required details. It adds them to the ticket as an internal note.

  3. Data sent through an API

    A Custom Action transfers the details through an API. The flow uses the response to determine what happens next.

  4. Record created

    The demo creates a record in Zendesk Custom Objects. For another destination system, its API and data requirements need to be checked.

The workflow also has a dedicated error path for requests that receive no response from the API.

Set it up in Zendesk

In the 20-minute document processing demo (recording in German, English subtitles available), Tim walks through the Action Builder, the agent’s instructions in the Agent Builder and the data transfer. He sets up the error path and tests the workflow.

The demo uses Zendesk Custom Objects as a sample database. To connect your CRM or ERP, you need suitable Zendesk integrations, fields and access rights.

2 Flag product recalls in tickets

An enquiry contains an order number. If it falls within the range affected by a product recall, the service team needs to know. The prepared Action Flow checks the range and adds an internal note. This fixed comparison does not require a Custom Agent.

Watch the recall check

3 Prepare Jira issues from enquiries

A customer reports a bug, but the development team does not need the entire ticket history. Tim explains an approach in which a Custom Agent prepares the relevant information and an Action Flow uses the Jira connection to create an issue.

Watch the Jira approach

4 Check eligibility for a reward

An invoice alone does not establish whether a reward can be paid. In the prepared example, an agent compares invoice details with business rules and reference data and explains its conclusion. The reference data is already attached to the ticket for the demo.

Watch the eligibility check

More use cases for your service team

Analysing documents, checking details and triggering follow-up actions can help with other tasks too. Depending on your data and integrations, possible applications include the following.

Review cancellation requests

An agent extracts details from the document; a flow retrieves contract data and checks your rules. Your team handles unclear matches and disputed cases.

Bring order status into the ticket

The ticket shows the status from your connected shop. An agent can first identify the order number in the enquiry; the order must be matched unambiguously.

File attachments

The document type and metadata determine where a file belongs. A suitable integration saves the attachment and its required details in the designated location.

An agent compares ticket content and prepares possible duplicates for review. Your rules determine whether the tickets may be merged.

Watch the full webinar with Zendesk

The 56-minute recording also includes Johannes Lober’s product overview and the questions raised during the webinar. The timestamps beside the video take you straight to each topic on YouTube.

Product screens and availability reflect the recording date; we can check the current options for your account.

Meet the speakers

  • Tim KopecTim Kopec
  • Maik IsernhinkeMaik Isernhinke
  • Dennis SchatteburgDennis Schatteburg
  • Johannes LoberJohannes Lober

Talk to me about your use case

Whether you work with documents, compare data or handle other recurring tasks, I’d be happy to look at how your service process works today and where you need support.

In a free introductory call, we’ll discuss your current setup and requirements. Together, we can work out how Leafworks could help and which next step makes sense.

Marvin Post

Marvin Post

Solution Hero

Scroll to Top