Cutt.ly

Shorten, brand, and measure links with Cutt.ly across both its personal and team API surfaces. Agents mint a tracked link per send and read click data back to see what actually landed.

1 trigger 16 actions API key available

Cutt.ly website ↗ Platform Documentation ↗ Capability data verified 2026-07-31

A campaign row is marked ready to send in the campaign tracker

The agent reads the row's owner field to decide whether the link belongs to one person or to the shared workspace

Shorten Team Link mints the link on the team's branded domain, so anyone on the team can repoint it later

Set Team Link Expiration caps the offer on the promotion's end date and names the fallback destination visitors get afterwards

The agent follows the short URL once and confirms it resolves to the intended landing page before the send goes out

The short URL, its expiry date and its fallback are written back onto the campaign row

The campaign owner approves the expiry date and the fallback, because both take effect silently on a URL that is already in someone's inbox

What This Integration Enables

Cutt.ly is the one connector in this category where the first question is not how to shorten a URL but whose link it is. The service runs two separate API surfaces. The Regular API creates links owned by a personal account. The Team API creates links that live in a shared workspace on a branded domain and can be seen and edited by every member. FlowRunner's connector consolidates both, which means the choice is explicit in the flow: Shorten Link and Shorten Team Link are different operations against different keys, and each has its own statistics, update, delete, password, expiration, mobile redirect and A/B test counterparts.

That distinction is worth designing around, because it decides what happens to a link months later. A campaign URL minted under a personal key is an orphan the day that person changes roles, and nobody else can repoint it. Beyond the ownership split, the connector covers the behaviors that make a short link more than a redirect: password protection, expiration by click count or calendar date with a fallback URL, per-platform mobile redirects including Android deferred deep linking, and A/B or A/B/C splits across two or three destinations behind one shared URL. On Link Clicks watches a link's traffic and emits an event carrying the new click count with the current breakdown by referrer, country, device, operating system, browser and language.

Without FlowRunner

Links belong to whoever made them A link minted on a personal account is invisible to the rest of the team

Expiry is a manual chore Offer links keep working past the promotion because nobody went back to switch them off

Variant tests need two URLs Comparing destinations means publishing two links and reconciling two reports

With FlowRunner

Ownership is chosen deliberately The workspace surface is picked at mint time, so the link survives the person who created it

Time limits are set at creation An offer link expires on its own date or click count, with a fallback that catches later visitors

One URL, several destinations A single distributed link splits traffic across variants and reports on all of them together

Use Case Scenarios

Every outbound send gets a team-owned link

A campaign is queued in HubSpot. Before it goes out, the agent calls Shorten Team Link for each destination in the send, reserving a readable alias on the team's branded domain and enabling public click statistics so anyone on the team can check performance without an admin. The resulting short URLs are written back into the campaign record. Six months later, when the landing page is replaced, whoever is on shift can call Update Team Link and repoint every one of them, because the links were never tied to an individual account.

One shared URL, three landing pages

A team wants to know which page converts, but the link is going into a printed insert and a podcast read where two URLs are not an option. The agent creates one link, then calls Set Team Link A/B Test with a chance percentage for the B variation and, if a third page is in play, for C. The remaining share continues to the original destination. Get Team Link Statistics is polled on a schedule and the results land in a Google Sheets comparison tab. One URL goes out, three destinations get measured.

Offer links that close themselves

A time-limited promotion needs its links dead when the promotion ends, and it needs the people who arrive late to land somewhere useful rather than on an error. The agent calls Set Link Expiration with the campaign's end date and a fallback URL pointing at the evergreen product page, or sets a click ceiling when the offer is capped by redemption rather than by date. On Link Clicks watches the traffic in the meantime, and when a link crosses its threshold the agent posts the current breakdown to Slack so the team knows the cap is close before it hits.

Human-in-Loop Highlight

Cutt.ly's delete does something most shorteners do not, and it is the reason cleanup gets a gate. Delete Link removes the link and its click history permanently, and it releases the alias for reuse. The URL does not just stop working. The alias goes back into the pool, and a stranger can claim it. Anything still carrying that short URL, a printed insert, an old newsletter, a QR code on a banner, now points at whatever the next person to claim the alias decides to serve. So when a housekeeping flow finds a link with no recent traffic, the agent gathers the evidence and stops, posting to Slack: "cutt.ly/spring-offer has 0 clicks in 90 days but still appears in the Q1 print insert. Deleting it frees the alias 'spring-offer' for anyone to claim, and the click history goes with it. Delete, or set an expiration with a fallback to the product page instead?" The person who knows what is still in circulation answers. The agent then executes either the delete or the safer expiration in one call. Cleanup that touches a namespace other people can take over is exactly the class of automation exceptions that FlowRunner is built to route to a human rather than resolve on its own.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via Slack

Human decides

Agent resumes with decision

Agent Capabilities

16 actions

Personal Links (Regular API)

Shorten Link Shortens a destination URL with the Regular API and returns the short link, its original URL, the page title and the creation date. Optionally reserves a custom alias, publishes on an approved branded domain, or exposes public click statistics.
Get Link Statistics Retrieves full click analytics for a link: total clicks, clicks from Facebook, X/Twitter and LinkedIn, bot traffic, per-referrer breakdowns and counts by country, device type, operating system, browser, device brand and language.
Update Link Edits an existing link without changing the short URL already distributed. Repoints it at a new destination, renames the alias, updates the title, assigns a tag, or changes how unique clicks are counted.
Delete Link Permanently deletes a link and its click history. The short URL stops resolving immediately and the alias is released for reuse. This cannot be undone.
Set Link Password Protects a link with a password so visitors must enter it before being redirected. Submitting an empty password removes the protection.
Set Link Expiration Configures automatic expiration after a number of clicks or on a calendar date, optionally sending later visitors to a fallback URL. Setting the condition to 0 removes an existing rule.
Set Link Mobile Redirect Routes visitors on a specific mobile platform to a dedicated destination, so one short link can open an Android app, an iOS app or a mobile web page. Also configures Android deferred deep linking.
Set Link A/B Test Splits traffic from one link across two or three destinations so variants compete under a single shared URL. The chance percentages for B and C cannot exceed 100 combined.

Team Links (Team API)

Shorten Team Link Shortens a destination URL through the Team API so the link belongs to the team workspace and is visible to every member. Supports a custom alias, any branded domain the team owns, public statistics, and a TRAI compliance header for links delivered by SMS in India.
Get Team Link Statistics Retrieves full click analytics for a team-owned link, with the same referrer, geography, device, browser and language breakdowns as the personal surface, optionally restricted to a date range.
Update Team Link Edits a team-owned link without changing the distributed short URL. This is the operation that lets anyone on the team repoint a campaign link long after the person who created it has moved on.
Delete Team Link Permanently deletes a team-owned link and its click history. The short URL stops resolving immediately and the alias is released for reuse.
Set Team Link Password Protects a team link with a password before redirection. Used for gated assets shared through a public channel.
Set Team Link Expiration Configures expiration for a team link by click count or calendar date, with an optional fallback URL for visitors who arrive after it closes.
Set Team Link Mobile Redirect Sends visitors on a given mobile platform to a dedicated destination from a team link, including Android deferred deep linking through an application package name and install referrer payload.
Set Team Link A/B Test Splits traffic from one team link across two or three destinations for variant comparison under a single shared URL.

Triggers

1 triggers

Event Triggers

On Link Clicks Fires when a Cutt.ly short link receives new clicks. Each cycle compares the link's total click count with the previous cycle and emits a single event carrying the number of new clicks together with the current breakdown by referrer, country, device, operating system, browser and language. The first cycle establishes a baseline and emits nothing.

Frequently Asked Questions

What can FlowRunner do with Cutt.ly?

FlowRunner agents can run Shorten Link, Get Link Statistics, and Update Link in Cutt.ly, plus 13 more actions.

Does connecting Cutt.ly to FlowRunner require OAuth?

No. Cutt.ly connects to FlowRunner with an API key, no OAuth flow required.

Can Cutt.ly trigger a FlowRunner workflow automatically?

Yes. Cutt.ly supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with Cutt.ly

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us