When new link created in Short.io, sync it to respond.io.
Whenever a new short link is created in Short.io, sync the link details to respond.io.
See all respond.io + Short.io 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.
respond.io Explore respond.io →
TriggersFires when a new text message is received in respond.io.
Fires when a new call comes in or out through respond.io.
Fires when a call is missed in respond.io.
Fires when a call recording finishes processing in respond.io.
Sends a text message through respond.io.
Starts an outbound call via respond.io.
Creates or updates a contact in respond.io.
Sends a recorded voice message via respond.io.
Short.io Explore Short.io →
TriggersFires when a shortened link created in Short.io is clicked.
Fires when a new shortened link is created in Short.io.
Creates a new shortened link in Short.io.
Tags a link's record in Short.io for tracking.
Retrieves click analytics for a link in Short.io.
Common questions
Can Knit build “When new link created in Short.io, sync it to respond.io.” between respond.io and Short.io?
Yes — describe it in the box above and Knit's Integrations Agent researches respond.io and Short.io'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.