When print job state change in PrintNode, sync it to ShipStation.
When a print job state changes in PrintNode, update the corresponding shipment record in ShipStation.
See all ShipStation + PrintNode integrations or talk to a human
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.
ShipStation Explore ShipStation →
TriggersFires when a new order or shipment is created in ShipStation.
Fires when a shipment is picked up, in transit or delivered in ShipStation.
Fires when a shipping label is created in ShipStation.
Creates a shipping or delivery order in ShipStation.
Creates a shipment and books the carrier in ShipStation.
Looks up the tracking status of a shipment in ShipStation.
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 print job state change in PrintNode, sync it to ShipStation.” between ShipStation and PrintNode?
Yes — describe it in the box above and Knit's Integrations Agent researches ShipStation 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.