Which tickets become board items?

Whatever your rule says. Most teams scope it to a tag or a status so only defects and tracked requests cross over, and leave routine questions and replies in Zendesk.

Does it sync the status back to Zendesk?

No. This is one-way, Zendesk to monday.com, create-only. Reflecting board status back into the ticket would mean adding an update_ticket step keyed on the ticket ID you stored.

Can it watch Zendesk continuously?

The server doesn't push, so the agent reads on a schedule. A half-hour loop catches new qualifying tickets without re-filing the ones already on the board.

Zendeskmonday.com

Create monday.com items from Zendesk tickets

A Zendesk + monday.com agent flow

A support ticket about a broken export is a real piece of work, but it sits in Zendesk where the people who'd fix it never look. Support reads tickets; product and ops track work on a monday.com board. This recipe carries the ones that need engineering or process work across, so they land where they get prioritized. Your agent calls get_tickets to read the latest from Zendesk, decides which describe a defect or a request worth tracking, and opens an item on your board with create_item: the subject as the name, the requester ID and ticket link in columns, a status. The Zendesk server answers calls rather than streaming, so the agent runs on a cadence you choose and only tickets that match your rule become board items.

The flow

Zendeskget_tickets

Fetch the latest tickets with pagination support.

monday.comcreate_item

Creates a new item in a board, optionally with column values.

Step by step

Set the board and the rule
Give the agent the monday.com board ID and what qualifies: maybe tickets with a 'bug' or 'feature-request' tag, or any open ticket older than a day with no resolution. Map ticket fields to board columns.
Pull the latest tickets
The agent calls get_tickets, which pages through recent tickets, and reads each subject, requester ID, status, and tags to apply your rule.
Create the board item
For each qualifying ticket it calls create_item with the subject as the item name and column values for the requester ID, the Zendesk ticket URL, and an initial status like 'New'.
Avoid double-filing
Store the Zendesk ticket ID against the monday.com item it created. On the next pass the agent skips tickets already on the board, so a long-open ticket isn't filed every run.

Tell your agent

Every 30 minutes, fetch the latest Zendesk tickets and pick the ones tagged 'bug' that aren't solved. For each one not already on the board, create a monday.com item on board 1234567890 with the ticket subject as the name, the requester ID and ticket link in their columns, and status 'New'. Skip tickets you've already filed.

Setup

This flow needs both servers connected to your agent. Follow each install guide:

Zendesk install guide monday.com install guide

Worth knowing

create_item maps your data to column values by column ID, not by the label you see in the UI. Fetch the board's columns once with get_board_schema and pass the real IDs, or the values silently land nowhere.
get_tickets returns the latest tickets and pages, so on a busy instance the agent must walk pages and apply your tag or status filter itself; there's no server-side query by tag here.
Zendesk ticket IDs and monday.com item IDs are different namespaces. Store the pairing yourself; neither side records the other's ID for you.

Questions

Which tickets become board items?: Whatever your rule says. Most teams scope it to a tag or a status so only defects and tracked requests cross over, and leave routine questions and replies in Zendesk.
Does it sync the status back to Zendesk?: No. This is one-way, Zendesk to monday.com, create-only. Reflecting board status back into the ticket would mean adding an update_ticket step keyed on the ticket ID you stored.
Can it watch Zendesk continuously?: The server doesn't push, so the agent reads on a schedule. A half-hour loop catches new qualifying tickets without re-filing the ones already on the board.