When get done jobs in Good2Go, sync it to Zendesk.
Create or update Zendesk tickets when done jobs are retrieved from Good2Go.
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.
Good2Go Explore Good2Go →
TriggersFires when a new print or mail job is submitted to Good2Go.
Fires when a print or mail job in Good2Go finishes or ships.
Sends a document or design to Good2Go to print.
Sends a physical postcard or letter via Good2Go.
Looks up the status of a print or mail job in Good2Go.
Zendesk Explore Zendesk →
TriggersFires when a new support ticket or chat conversation starts 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 a reply or internal note on a ticket or conversation in Zendesk.
Common questions
Can Knit build “When get done jobs in Good2Go, sync it to Zendesk.” between Good2Go and Zendesk?
Yes — describe it in the box above and Knit's Integrations Agent researches Good2Go 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.