When get last urls in Cutt.ly, sync it to Trello.
When recent URLs are retrieved in Cutt.ly, post short links as comments on Trello cards.
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.
Cutt.ly Explore Cutt.ly →
TriggersFires when a shortened link created in Cutt.ly is clicked.
Fires when a new shortened link is created in Cutt.ly.
Creates a new shortened link in Cutt.ly.
Tags a link's record in Cutt.ly for tracking.
Retrieves click analytics for a link in Cutt.ly.
Trello Explore Trello →
TriggersFires when a new task, job or item is created in Trello.
Fires when a task in Trello is marked complete.
Fires when a task's due date in Trello is coming up.
Fires when a task, job or project changes status in Trello.
Creates a new task, job or item in Trello.
Updates a task's status or assignee in Trello.
Posts a comment on a task in Trello.
Assigns a task in Trello to a team member.
Common questions
Can Knit build “When get last urls in Cutt.ly, sync it to Trello.” between Cutt.ly and Trello?
Yes — describe it in the box above and Knit's Integrations Agent researches Cutt.ly and Trello'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.