Zendesk · Arazzo Workflow

Zendesk Apply Macro to Ticket

Version 1.0.0

Preview the changes a macro would make to a ticket, then commit them.

1 workflow 2 source APIs 1 provider
View Spec View on GitHub ChatCRMHelp CenterSellSupportT1TalkTicketingTicketsArazzoWorkflows

Provider

zendesk

Workflows

apply-macro-to-ticket
Preview a macro against a ticket and persist its resulting changes.
Requests the macro preview for a ticket and then commits the resulting status and comment back to the ticket.
2 steps inputs: macroId, ticketId outputs: ticketId, ticketStatus
1
previewMacro
{$sourceDescriptions.macrosApi.url}#/paths/~1api~1v2~1tickets~1{ticket_id}~1macros~1{macro_id}~1apply/get
Request the ticket as it would appear after applying the macro. This does not change the ticket; it returns the proposed changes. The operationId ShowTicketAfterChanges is non-unique across the sourced specs, so it is referenced by operationPath against the macros description.
2
commitChanges
UpdateTicket
Persist the macro's proposed status and comment to the ticket.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Zendesk Apply Macro to Ticket
  summary: Preview the changes a macro would make to a ticket, then commit them.
  description: >-
    Zendesk macros are applied client-side: the API returns the ticket changes a
    macro would produce, and the caller then persists them. This workflow first
    requests the macro preview for a ticket, capturing the resulting status and
    comment body, and then commits those changes back to the ticket through a
    ticket update using the documented {ticket:{...}} envelope.
  version: 1.0.0
sourceDescriptions:
- name: macrosApi
  url: ../openapi/macros-openapi-original.yml
  type: openapi
- name: ticketsApi
  url: ../openapi/tickets-openapi-original.yml
  type: openapi
workflows:
- workflowId: apply-macro-to-ticket
  summary: Preview a macro against a ticket and persist its resulting changes.
  description: >-
    Requests the macro preview for a ticket and then commits the resulting
    status and comment back to the ticket.
  inputs:
    type: object
    required:
    - ticketId
    - macroId
    properties:
      ticketId:
        type: integer
        description: The id of the ticket to apply the macro to.
      macroId:
        type: integer
        description: The id of the macro to apply.
  steps:
  - stepId: previewMacro
    description: >-
      Request the ticket as it would appear after applying the macro. This does
      not change the ticket; it returns the proposed changes. The operationId
      ShowTicketAfterChanges is non-unique across the sourced specs, so it is
      referenced by operationPath against the macros description.
    operationPath: '{$sourceDescriptions.macrosApi.url}#/paths/~1api~1v2~1tickets~1{ticket_id}~1macros~1{macro_id}~1apply/get'
    parameters:
    - name: ticket_id
      in: path
      value: $inputs.ticketId
    - name: macro_id
      in: path
      value: $inputs.macroId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      proposedStatus: $response.body#/result/ticket/status
      proposedComment: $response.body#/result/ticket/comment/body
  - stepId: commitChanges
    description: Persist the macro's proposed status and comment to the ticket.
    operationId: UpdateTicket
    parameters:
    - name: ticket_id
      in: path
      value: $inputs.ticketId
    requestBody:
      contentType: application/json
      payload:
        ticket:
          status: $steps.previewMacro.outputs.proposedStatus
          comment:
            body: $steps.previewMacro.outputs.proposedComment
            public: true
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      ticketId: $response.body#/ticket/id
      ticketStatus: $response.body#/ticket/status
  outputs:
    ticketId: $steps.commitChanges.outputs.ticketId
    ticketStatus: $steps.commitChanges.outputs.ticketStatus

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/zendesk-apply-macro-to-ticket-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.