When get last urls in Cutt.ly, sync it to Mobile Message.
When recent URLs are fetched in Cutt.ly, send SMS text messages via Mobile Message.
See all Cutt.ly + Mobile Message 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.
Mobile Message Explore Mobile Message →
TriggersFires when a new text message is received in Mobile Message.
Fires when a new call comes in or out through Mobile Message.
Fires when a call is missed in Mobile Message.
Fires when a call recording finishes processing in Mobile Message.
Sends a text message through Mobile Message.
Starts an outbound call via Mobile Message.
Creates or updates a contact in Mobile Message.
Sends a recorded voice message via Mobile Message.
Common questions
Can Knit build “When get last urls in Cutt.ly, sync it to Mobile Message.” between Cutt.ly and Mobile Message?
Yes — describe it in the box above and Knit's Integrations Agent researches Cutt.ly and Mobile Message'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.