When new ticket created in Enchant, sync it to Parseur.
When a new ticket is created in Enchant, send the ticket content to Parseur for parsing.
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.
Enchant Explore Enchant →
TriggersFires when a new support ticket or chat conversation starts in Enchant.
Fires when a ticket's status changes in Enchant.
Fires when a ticket in Enchant is assigned to an agent.
Fires when a ticket in Enchant breaches its response SLA.
Creates a new ticket in Enchant.
Updates a ticket's status in Enchant.
Assigns a ticket in Enchant to an agent.
Posts a reply or internal note on a ticket or conversation in Enchant.
Parseur Explore Parseur →
TriggersFires when Parseur finishes extracting data from a document such as an invoice, receipt, form or resume.
Posts a file to Parseur to be parsed.
Runs an extraction template in Parseur against a document.
Common questions
Can Knit build “When new ticket created in Enchant, sync it to Parseur.” between Enchant and Parseur?
Yes — describe it in the box above and Knit's Integrations Agent researches Enchant and Parseur'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.