When contact deleted in YoPrint, sync it to Ink.Works.
When a contact is deleted in YoPrint, sync the deletion to Ink.Works.
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.
YoPrint Explore YoPrint →
TriggersFires when a new print or mail job is submitted to YoPrint.
Fires when a print or mail job in YoPrint finishes or ships.
Sends a document or design to YoPrint to print.
Sends a physical postcard or letter via YoPrint.
Looks up the status of a print or mail job in YoPrint.
Ink.Works Explore Ink.Works →
TriggersFires when a new page or doc is created in Ink.Works.
Fires when a new record is added to a database or table in Ink.Works.
Fires when a doc in Ink.Works is published or shared.
Fires when a status field changes on a record in Ink.Works.
Starts a new page in Ink.Works from a saved template.
Creates or updates a record in Ink.Works.
Adds text to the end of an existing doc in Ink.Works.
Moves a page in Ink.Works into a different space.
Common questions
Can Knit build “When contact deleted in YoPrint, sync it to Ink.Works.” between YoPrint and Ink.Works?
Yes — describe it in the box above and Knit's Integrations Agent researches YoPrint and Ink.Works'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.