When get last urls in Cutt.ly, sync it to SQL Server.
When recent URLs are fetched in Cutt.ly, save link logs into a SQL Server database.
See all Cutt.ly + SQL Server 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.
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.
SQL Server Explore SQL Server →
TriggersFires when a new row is added to a table in SQL Server.
Fires when an existing row changes in SQL Server.
Fires when a scheduled query in SQL Server finishes running.
Runs a SQL query against SQL Server and returns the result.
Writes a new or updated row to SQL Server.
Syncs a table in SQL Server with data from another source.
Common questions
Can Knit build “When get last urls in Cutt.ly, sync it to SQL Server.” between Cutt.ly and SQL Server?
Yes — describe it in the box above and Knit's Integrations Agent researches Cutt.ly and SQL Server'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.