When new link in BL.INK, sync it to SQL Server.
When a new link is created in BL.INK, save URL and click tracking metadata to SQL Server.
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.
BL.INK Explore BL.INK →
TriggersFires when a shortened link created in BL.INK is clicked.
Fires when a new shortened link is created in BL.INK.
Creates a new shortened link in BL.INK.
Tags a link's record in BL.INK for tracking.
Retrieves click analytics for a link in BL.INK.
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 new link in BL.INK, sync it to SQL Server.” between BL.INK and SQL Server?
Yes — describe it in the box above and Knit's Integrations Agent researches BL.INK 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.