When tag added to post in Canny, sync it to Tny.
When a tag is added to a post in Canny, update the record in Tny.
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.
Tny Explore Tny →
TriggersFires when a shortened link created in Tny is clicked.
Fires when a new shortened link is created in Tny.
Creates a new shortened link in Tny.
Tags a link's record in Tny for tracking.
Retrieves click analytics for a link in Tny.
Canny Explore Canny →
TriggersFires when a new task or card is created in Canny.
Fires when a task in Canny is marked complete.
Fires when a task's due date in Canny is coming up.
Fires when a comment is added to a task in Canny.
Creates a new task in Canny.
Updates a task's status or assignee in Canny.
Posts a comment on a task in Canny.
Moves a task in Canny to a different board or list.
Common questions
Can Knit build “When tag added to post in Canny, sync it to Tny.” between Tny and Canny?
Yes — describe it in the box above and Knit's Integrations Agent researches Tny and Canny'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.