Forward critical SLA breaches to secondary queues
When an SLA is breached in Document360, automatically create an urgent ticket in Zoho Desk and assign it to senior technical staff.
See all Document360 + Zoho Desk integrations or talk to a human
Opens Claude with Knit filled in: click Continue. Claude web and desktop share one connector list. Or paste this link in Settings > Connectors > Add custom connector.
curl -fsSL https://raw.githubusercontent.com/knitapi/knit-plugin/main/plugins/knit/skills/knit/scripts/install.sh | bash -s -- --agents claude
Run in your own terminal, then restart Claude Code. Adds the server, the Knit skill and a CLAUDE.md note.
Turn on developer mode, then create a connector named Knit with this link and No Auth.
curl -fsSL https://raw.githubusercontent.com/knitapi/knit-plugin/main/plugins/knit/skills/knit/scripts/install.sh | bash -s -- --agents codex
Run in your own terminal (not through Codex), then start a new Codex session.
curl -fsSL https://raw.githubusercontent.com/knitapi/knit-plugin/main/plugins/knit/skills/knit/scripts/install.sh | bash -s -- --agents antigravity
Run in your own terminal, then reload MCP servers (/mcp in the CLI, refresh in the IDE).
curl -fsSL https://raw.githubusercontent.com/knitapi/knit-plugin/main/plugins/knit/skills/knit/scripts/install.sh | bash -s -- --agents cursor
Run in your own terminal, restart Cursor, then paste the note it prints into User Rules.
Google for Startups AcceleratorHow Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
Document360 Explore Document360 →
TriggersFires when a new support ticket or chat conversation starts in Document360.
Fires when a ticket's status changes in Document360.
Fires when a ticket in Document360 is assigned to an agent.
Fires when a ticket in Document360 breaches its response SLA.
Creates a new ticket in Document360.
Updates a ticket's status in Document360.
Assigns a ticket in Document360 to an agent.
Posts a reply or internal note on a ticket or conversation in Document360.
Zoho Desk Explore Zoho Desk →
TriggersFires when a new support ticket or chat conversation starts in Zoho Desk.
Fires when a ticket's status changes in Zoho Desk.
Fires when a ticket in Zoho Desk is assigned to an agent.
Fires when a ticket in Zoho Desk breaches its response SLA.
Creates a new ticket in Zoho Desk.
Updates a ticket's status in Zoho Desk.
Assigns a ticket in Zoho Desk to an agent.
Posts a reply or internal note on a ticket or conversation in Zoho Desk.
More Document360 + Zoho Desk workflows
See all Document360 + Zoho Desk integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Forward critical SLA breaches to secondary queues” between Document360 and Zoho Desk?
Yes — describe it in the box above and Knit's Integrations Agent researches Document360 and Zoho Desk's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.
Why sync tickets across two separate ticketing platforms?
It allows customer support, engineering, and external vendor teams to collaborate in their preferred ticketing platforms without manual status updates or missed context.
Do comments and status changes mirror bidirectionally?
Yes, status updates or newly assigned tickets in one platform can immediately update the corresponding issue in the second platform.