When new template in PublisherKit, sync it to Readwise.
When a new template is created in PublisherKit, save textual quote snippets to Readwise.
See all Readwise + PublisherKit 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.
Readwise Explore Readwise →
TriggersFires when a new page or article is saved in Readwise.
Fires when a saved item in Readwise is tagged or archived.
Saves a page or link to Readwise.
Tags a saved item's record in Readwise.
PublisherKit Explore PublisherKit →
TriggersFires when a new file or board is created in PublisherKit.
Fires when someone comments on a file in PublisherKit.
Fires when a file in PublisherKit is shared with someone new.
Fires when a file in PublisherKit is marked ready for review.
Starts a new file in PublisherKit from a saved template.
Posts a comment on a specific file in PublisherKit.
Exports a frame or board from PublisherKit as a PNG or PDF.
Moves a file in PublisherKit into a different project or folder.
Common questions
Can Knit build “When new template in PublisherKit, sync it to Readwise.” between Readwise and PublisherKit?
Yes — describe it in the box above and Knit's Integrations Agent researches Readwise and PublisherKit'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.