Tny
Analytics & DataCreate and manage short links with Tny by Chief Tools on shared or custom domains, reading human and crawler click counts separately. Agents measure real engagement rather than bot traffic.
What This Integration Enables
Tny, from Chief Tools, separates human clicks from crawler visits and reports them as two counters on every link. That sounds like a detail and it is not, because it changes what your numbers mean. Any link you post into a chat tool, share on a social network or send through a corporate mail gateway is fetched automatically before a person ever sees it: preview services unfurl it, security scanners open it, indexers crawl it. A shortener that reports one combined total is quietly telling you those fetches were interest. Tny is the connector in this catalog that lets an agent report on the traffic that could have converted, which is the only kind worth reallocating a budget over.
The rest of the surface follows from that honesty. Agents shorten URLs on the shared Tny domains or on a verified custom domain, read a link back by internal ID or by slug, and list links with a free text search where every entry carries both counters. Set Social Media Card controls the title and description a link shows when it is shared, so an unfurled preview reads as your campaign rather than as whatever the destination page happens to have in its head tag. Unshorten URL is the outlier and the most useful thing here for anyone who does not think of themselves as a marketer: it resolves any shortened or redirecting URL, from any shortener, following the whole chain including meta refresh redirects, returning every hop with its status code and optionally stripping known tracking parameters. Two behaviours are worth knowing before you build. Tny de-duplicates by destination, so shortening a URL it has already shortened returns the existing link and ignores the slug and comment you passed. And a custom slug is only allowed together with a custom domain. Together they mean per campaign links to the same landing page need a custom domain, or two campaigns will silently share one counter.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The weekly report where the totals would have lied
Every Monday the agent lists the account's links and pulls both counters for each. It builds the ranked table from human clicks, and beside each row it shows the crawler visits so nobody has to take the adjustment on trust. Two links that looked like the week's best performers turn out to have been posted into channels where every message is unfurled by a preview service. The table lands in Slack and a copy goes to Google Sheets so the trend survives the week. The budget conversation starts from a number that means what it says.
Resolving a link before the workflow follows it
An inbound message arrives carrying a shortened URL that nobody recognizes. Before any downstream step opens or forwards it, the agent calls Unshorten URL and gets the full redirect chain back, every hop with its HTTP status code, with known tracking parameters stripped from the final destination. A chain that resolves cleanly to a known vendor domain continues automatically. A chain that hops through three unrelated hosts, or ends somewhere the workflow has never seen, is posted to the security channel with the hops laid out and goes no further until a person looks at it.
Campaign links that do not collapse into each other
A campaign runs the same landing page across email through Brevo and across LinkedIn, and the team wants the two counted apart. Because Create Link de-duplicates by destination on the shared domains, the agent resolves the account's verified domains with List Link Domains first and mints each variant on a custom domain with its own slug, which is the only combination Tny allows a custom slug with. It then calls Set Social Media Card on each link so the unfurled preview carries the campaign's own title and description rather than the page's default, and writes both short URLs back to the campaign record.
Human-in-Loop Highlight
The gate on Tny is not a delete or a write. It is the moment a number becomes a decision. When the agent has finished the weekly pull and one of the top links turns out to be mostly crawler traffic, it does not silently drop that link from the ranking, and it does not report the total either. Silently correcting is as bad as being wrong, because the person reading the table has no way to see that a judgment was made on their behalf. So the agent stops and puts the discrepancy in front of the budget owner with both figures intact: "The Q3 offer link is second by total visits and eighth by human clicks. Most of the gap is crawler traffic from the channel it was posted in. Rank the report by human clicks, or by total, and should the reallocation use the same basis?" A person answers once, the agent applies that basis to the whole report, and the choice is on the record next to the numbers it produced. This is the difference between automation that hands you an answer and Orchestration as a Service, where the agent does the collection and the arithmetic and a person still owns the judgment that money follows. Delete Link By ID and Delete Link By Slug sit behind the same discipline for a simpler reason: both are permanent, the short URL stops resolving immediately, and the click history goes with it.
Agent Capabilities
13 actionsLinks
6- Create Link Shortens a URL into a Tny link, optionally on a custom domain, with a custom slug that is only permitted alongside a custom domain, and an internal comment. Tny de-duplicates by destination, so shortening a URL it already holds returns the existing link and ignores the slug and comment. Used as the mint step, and worth pairing with a custom domain whenever two campaigns need separate counters on the same page.
- Get Link By ID Retrieves one link by its internal identifier with the destination, human click and crawler visit counts, custom domain, social media card and creation metadata. Returns nothing when no link with that identifier exists. Used when the workflow already holds the identifier from creation.
- Get Link By Slug Retrieves the same record by slug, optionally scoped to a custom domain. Used when all the flow has is the short URL somebody pasted, and it needs the destination, the counters or the identifier behind it.
- List Links Lists the account's links with page based pagination and an optional free text search across link details, each entry carrying both the click counter and the crawler visit counter. Used to build the working set for any report, which is the operation the weekly performance flow starts from.
- Delete Link By ID Permanently destroys a link by its internal identifier. The short URL stops resolving immediately and the click history is removed. Used at genuine end of life, behind a human decision.
- Delete Link By Slug Permanently destroys a link identified by its slug and, on a custom domain, the domain it belongs to. Same permanence and the same gate. Used when the flow holds the short URL rather than the identifier.
Social Media Cards
2- Set Social Media Card Sets the title and description shown when a link is unfurled on social networks and chat apps, both of which are required. The card image keeps whatever was uploaded through the Tny interface, or falls back to the default. Used so a shared campaign link previews as the campaign rather than as the destination page's own metadata.
- Remove Social Media Card Removes the custom card so previews fall back to the destination page's metadata. Safe to call on links that never had one. Used when a campaign ends and the link should stop presenting itself as that campaign.
Utilities
1- Unshorten URL Resolves any shortened or redirecting URL to its final destination by following the complete chain, including HTTP redirects and meta refresh redirects, returning every hop with its status code and optionally stripping known tracking parameters such as UTM tags. Works on links from any shortener, not only Tny. Used to establish where an inbound link actually goes before a workflow follows, forwards or stores it.
Domains and Account
4- List Link Domains Lists the custom domains configured for shortening, including which is the default and how each handles redirects. Used to resolve the domain a link should be minted on, which is also the prerequisite for using a custom slug.
- List Domain Redirects Lists the account's custom domains that redirect visitors elsewhere, with their target, path and query forwarding settings and visit counters. These are domain level redirects rather than individual links. Used when auditing what a brand hostname does with traffic that does not match a link.
- List Global Domains Lists the shared Tny domains any account can shorten on. Combined with List Link Domains it gives the full set of hostnames available to a create step.
- Get Account Returns the account the API token authenticates as, with team name, timezone and creation date. A token that is invalid, expired or missing the required scope resolves to no account at all, which makes this the reliable connection check before a scheduled run.
Frequently Asked Questions
What can FlowRunner do with Tny?
FlowRunner agents can run Create Link, Get Link By ID, and Get Link By Slug in Tny, plus 10 more actions.
Does connecting Tny to FlowRunner require OAuth?
No. Tny connects to FlowRunner with an API key, no OAuth flow required.
Can Tny trigger a FlowRunner workflow automatically?
Tny doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Tny
$100 in credits. No card required. Connect in minutes.