Update ticket status when documentation status changes
When a document's status changes in Tettra, automatically update the corresponding ticket status in Zendesk to reflect progress.
4.9/5 on G2·
Google for Startups Accelerator
How 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.
Tettra Explore Tettra →
TriggersFires when a new page or doc is created in Tettra.
Fires when a new record is added to a database or table in Tettra.
Fires when a doc in Tettra is published or shared.
Fires when a status field changes on a record in Tettra.
Starts a new page in Tettra from a saved template.
Creates or updates a record in Tettra.
Adds text to the end of an existing doc in Tettra.
Moves a page in Tettra into a different space.
Zendesk Explore Zendesk →
TriggersFires when a new support ticket is created in Zendesk.
Fires when a ticket's status changes in Zendesk.
Fires when a ticket in Zendesk is assigned to an agent.
Fires when a ticket in Zendesk breaches its response SLA.
Creates a new ticket in Zendesk.
Updates a ticket's status in Zendesk.
Assigns a ticket in Zendesk to an agent.
Posts an internal or public comment on a ticket in Zendesk.
More Tettra + Zendesk workflows
Log ticket SLA breaches into incident docs
When an SLA is breached in Zendesk, automatically append the breach details to your incident log page in Tettra for team post-mortems.
See details
Create support tickets from published documentation
When a new page is created in Tettra, automatically create a tracking ticket in Zendesk so team members can review and approve it.
See details
See all Tettra + Zendesk integrations → · Browse the full workflow library →
Common questions
Can Knit build “Update ticket status when documentation status changes” between Tettra and Zendesk?
Yes — describe it in the box above and Knit's Integrations Agent researches Tettra and Zendesk'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 pair Tettra and Zendesk?
Connecting these apps bridges support operations and knowledge management, allowing support tickets and team documentation to stay synchronized effortlessly.
Can SLA warnings in Zendesk alert our team inside Tettra?
When an SLA is breached in Zendesk, you can automatically append warning details or update project records in Tettra to escalate the issue.