When new unsubscriber in Curated, sync it to thanks.io.
When a subscriber unsubscribes in Curated, trigger a follow-up postcard via thanks.io.
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.
thanks.io Explore thanks.io →
TriggersFires when a new print or mail job is submitted to thanks.io.
Fires when a print or mail job in thanks.io finishes or ships.
Sends a document or design to thanks.io to print.
Sends a physical postcard or letter via thanks.io.
Looks up the status of a print or mail job in thanks.io.
Curated Explore Curated →
TriggersFires when a new subscriber is added in Curated.
Fires when a contact unsubscribes in Curated.
Fires when a subscriber opens or clicks a campaign in Curated.
Creates or updates a subscriber in Curated.
Unsubscribes a contact in Curated.
Adds a subscriber to a list or segment in Curated.
Sends a one-off transactional email via Curated.
Common questions
Can Knit build “When new unsubscriber in Curated, sync it to thanks.io.” between thanks.io and Curated?
Yes — describe it in the box above and Knit's Integrations Agent researches thanks.io and Curated'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.