When something happens in Tny, sync it to HubSpot.
When a URL is shortened in Tny, attach the shortened link to the contact or deal record in HubSpot.
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.
HubSpot Explore HubSpot →
TriggersFires when a new lead or contact is created in HubSpot.
Fires when a deal moves to a new stage in HubSpot.
Fires when a deal is marked won in HubSpot.
Fires when a field on a contact changes in HubSpot.
Creates or updates a contact in HubSpot.
Creates a new deal in HubSpot.
Moves a deal to a new stage in HubSpot.
Logs a call, email, or note against a record in HubSpot.
Common questions
Can Knit build “When something happens in Tny, sync it to HubSpot.” between Tny and HubSpot?
Yes — describe it in the box above and Knit's Integrations Agent researches Tny and HubSpot'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.