When new form submission received in Sniply, sync it to Shorten.REST.
When a form submission is received in Sniply, shorten URL payloads using Shorten.REST.
See all Shorten.REST + Sniply 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.
Shorten.REST Explore Shorten.REST →
TriggersFires when a shortened link created in Shorten.REST is clicked.
Fires when a new shortened link is created in Shorten.REST.
Creates a new shortened link in Shorten.REST.
Tags a link's record in Shorten.REST for tracking.
Retrieves click analytics for a link in Shorten.REST.
Sniply Explore Sniply →
TriggersFires when a shortened link created in Sniply is clicked.
Fires when a new shortened link is created in Sniply.
Creates a new shortened link in Sniply.
Tags a link's record in Sniply for tracking.
Retrieves click analytics for a link in Sniply.
Common questions
Can Knit build “When new form submission received in Sniply, sync it to Shorten.REST.” between Shorten.REST and Sniply?
Yes — describe it in the box above and Knit's Integrations Agent researches Shorten.REST and Sniply'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.