src ▸ task opened 0

Automate Zendesk

Turn the repetitive Zendesk work you do by hand (open a view, read tickets by filter) into a workflow Writ runs for you, on your own account, on a schedule or on demand.

Automate Zendesk See how it works
Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.
Zendesk workflow
  1. 1
    open a view
  2. 2
    read tickets by filter
  3. 3
    export a report
  4. 4
    update a ticket

✓ Recorded once, then run for you

gap ▸ done by hand 01
01
why

Stop doing Zendesk by hand

The Zendesk tasks you repeat (open a view, read tickets by filter, export a report) are exactly the kind of work a computer should do. But Zendesk only exposes part of it through an API, and the flow runs behind a login and dynamic pages. Zendesk has an API, but Explore reports and some admin screens are only reachable through the browser UI.

Writ closes that gap. Record the Zendesk task once (or describe it to an AI session) and Writ runs it for you in a real browser, on your own account. Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.

ops ▸ actions mapped 02
02
automate

Zendesk tasks Writ can run for you

Each of these is a real Zendesk action, captured into a workflow and run on your own account.

{ }open a view
{ }read tickets by filter
{ }export a report
{ }update a ticket

Workflows extract structured fields such as ticket, status, assignee, satisfaction score along the way: typed data you can route anywhere.

build ▸ three routes 03
03
build

Three ways to build your Zendesk automation

Pick whichever fits the task. All three produce the same workflow Writ can run for you.

✦Record itDo the Zendesk task once in a real browser (open a view, then read tickets by filter) and the recorder captures every step into a reusable workflow.
✦Describe it to AITell an AI session your goal on Zendesk in plain language; it drives the live page and builds the workflow for you, no recording needed.
✦Discover itLet API discovery watch Zendesk's own network calls as you browse, then turn the underlying requests into a fast, headless workflow.

Built on the same engine as the recorder and workflows, with 30+ step types.

auth ▸ logged-in web 04
04
the hard web

Login, 2FA, and dynamic pages on Zendesk

The reason Zendesk is tedious to automate is the same reason most tools can't. Writ handles it.

Writ signs into your own Zendesk instance through a Persona, including SSO, and runs inside that session.

PersonasTOTP & mailbox OTP AI navigationReal Chromium rendering
when ▸ it runs 05
05
when it runs

Run the Zendesk automation on your terms

On a schedule, on demand, or the instant something changes. You choose the trigger.

✦On a scheduleRun the Zendesk task every hour, every morning, or any cadence. No one has to remember to do it.
✦On demandTrigger a single run from the dashboard, a webhook, your code, or an AI agent, whenever you need it.
✦On a changeWatch Zendesk for ticket status change or new ticket in a view and fire the automation the instant it happens.
  1. 1
    Build the Zendesk workflow once

    Record the task, describe it to AI, or discover it from the network. Writ captures each step, including login and 2FA, into a workflow you can edit.

  2. 2
    Run it on your terms

    Run it on demand, on a schedule, or fire it from a Monitor when Zendesk changes. It runs on your own Zendesk account, in a real browser.

  3. 3
    Call it from anything

    The same workflow is a REST endpoint at /v1/zendesk/run and an MCP tool, so your code, a no-code tool, or an AI agent can trigger the Zendesk automation too.

watch ▸ changes tracked 06
06
watch

Trigger the Zendesk automation on a change

Monitor Zendesk for ticket status change, new ticket in a view, satisfaction-score change and run your workflow the moment it happens.

Monitors check as fast as every 10s (10s on Enterprise). A detected change becomes a trigger that runs your Zendesk automation in seconds. Monitor Zendesk ▸

venue ▸ local or cloud 07
07
run it

Free on your own machine, or on cloud

Local / BYO agent

No compute charge. The agent runs on your hardware, so it can reach Zendesk even from an intranet or VPN-only network, and your AI keys never leave your machine.

Writ cloud

Metered by running time at $0.12 per browser-hour, drawn from your plan’s included usage. No infrastructure to manage.

call ▸ endpoint too 08
08
callable

The same Zendesk automation is an API and an MCP tool

Automating Zendesk for yourself and calling it from software are the same workflow. Once you have it, publish it as a REST endpoint at/v1/zendesk/run and a matching MCP tool, so your code or an AI agent can trigger the Zendesk task too.

Zendesk API Zendesk MCP tools
also ▸ same workflow 09
09
other ways

Other ways to work with Zendesk

Zendesk APICall Zendesk as a REST endpoint from your own software.Website to API Zendesk MCP toolsExpose Zendesk as MCP tools your agent can call.For AI agents Monitor ZendeskWatch Zendesk and act the instant it changes.Change detection WorkflowsHow recorded workflows run, with login, 2FA, and 30+ step types.Product
faq ▸ questions answered 10
10
faq

Automating Zendesk: questions

How do I automate Zendesk?
Record the Zendesk task once in the recorder (open a view, read tickets by filter, export a report) or describe your goal to an AI session. Writ turns it into a workflow it can run for you on a schedule or on demand, on your own Zendesk account. It usually takes minutes, not a backend project.
Is it allowed to automate Zendesk this way?
Use Writ on your own Zendesk instance. Authorized automation of your own account. Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.
Does Zendesk automation work behind login and 2FA?
Writ signs into your own Zendesk instance through a Persona, including SSO, and runs inside that session. Writ handles TOTP and mailbox-OTP two-factor through Personas, so the automation runs inside your own authenticated Zendesk session.
Can I run the Zendesk automation without writing code?
Yes. Recording and AI sessions need no code at all. If you do want to trigger it from software, the same workflow is a REST endpoint and an MCP tool, but that is optional.
Where does it run, and what does it cost?
Run it on your own machine with a local or BYO agent for no compute charge, useful when Zendesk is only reachable from your network or VPN. Or run it on metered cloud at $0.12 per browser-hour, drawn from your plan’s included usage. Start free.
rec ▸ ready ●

Automate Zendesk in minutes

Record it once, then let Writ run it for you: on a schedule, on demand, or on a change. Get started free.

Get started