When something happens in Tny, sync it to Klaviyo.
When a short URL is created in Tny, sync the link properties to Klaviyo for email campaigns.
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.
Tny Explore Tny →
TriggersFires when a shortened link created in Tny is clicked.
Fires when a new shortened link is created in Tny.
Creates a new shortened link in Tny.
Tags a link's record in Tny for tracking.
Retrieves click analytics for a link in Tny.
Klaviyo Explore Klaviyo →
TriggersFires when a new lead or contact is captured in Klaviyo.
Fires when a contact enters an automation in Klaviyo.
Fires when a field on a contact changes in Klaviyo.
Fires when a contact unsubscribes in Klaviyo.
Creates or updates a contact in Klaviyo.
Adds a contact to a workflow or campaign in Klaviyo.
Sends an email or message to a contact via Klaviyo.
Changes a contact's tags in Klaviyo.
Common questions
Can Knit build “When something happens in Tny, sync it to Klaviyo.” between Tny and Klaviyo?
Yes — describe it in the box above and Knit's Integrations Agent researches Tny and Klaviyo'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.