When new customer in Zid, sync it to PrintNode.
When a new customer registers in Zid, print a welcome packing label or receipt via PrintNode.
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.
Zid Explore Zid →
TriggersFires when a customer places a new order in Zid.
Fires when an order in Zid is paid, fulfilled, refunded or disputed.
Fires when a new customer account is created in Zid.
Fires when a customer abandons their cart before completing checkout in Zid.
Creates or updates a product or listing in Zid.
Updates an order's status or fulfillment details in Zid.
Sends a custom API request to Zid for actions not covered by a dedicated action.
PrintNode Explore PrintNode →
TriggersFires when a new print or mail job is submitted to PrintNode.
Fires when a print or mail job in PrintNode finishes or ships.
Sends a document or design to PrintNode to print.
Sends a physical postcard or letter via PrintNode.
Looks up the status of a print or mail job in PrintNode.
Common questions
Can Knit build “When new customer in Zid, sync it to PrintNode.” between Zid and PrintNode?
Yes — describe it in the box above and Knit's Integrations Agent researches Zid and PrintNode'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.