Resources · Make integration

Cuttly Make integrationAutomate Cuttly with Make.

Every new link your team publishes can come out short, tagged and ready to track. The Cuttly Make integration gives you 9 action modules to shorten, edit and measure links. This page shows how to plug in your API key and build a first scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Cuttly Make integration do for you?

The Cuttly Make integration links your Cuttly account to Make so a scenario (the automation you build in Make, a chain of steps) can create and manage short links for you. Each step is a module: here, 9 actions that shorten a link, change it or read its statistics, without writing code.

Short links that appear on their own. A new row lands in a spreadsheet or a new post is published in another app: Shorten an URL returns the short version, and Create a tag files it under the right campaign so nobody sorts links by hand.

Campaign links you can fix after launch. A landing page moves? Update Source URL points the existing short link to the new address, and Update UTM rewrites its tracking parameters, so the link already printed or shared keeps working.

Click numbers where your team already looks. Get an URL Analytics reads the statistics of a short link and passes them to the next module, a sheet or a message, for example.

One thing to know: Cuttly has no trigger in Make. A scenario always starts from another app or from a schedule. The Make review explains how Make works overall, and if you also weigh n8n, the n8n vs Make comparison lays out both tools side by side.

Connect

How do you connect Cuttly to Make?

  1. 01

    Copy your Cuttly API key

    You need an active Cuttly account first. Log in, open the Edit Account page, click the option that generates an API key, then copy the key shown on screen. Keep it at hand for the next step.

  2. 02

    Add a Cuttly module

    In Make, open your scenario, add any Cuttly module and click Create a connection. A connection is your Cuttly account linked to Make once, then reused by every Cuttly module you add later.

  3. 03

    Paste the key and save

    Give the connection a name in Connection name if you want (it is optional), paste the API key you copied, and confirm. Make then uses this account for every action in the scenario.

First scenario

Your first scenario with Cuttly

GoalWhen a new link shows up in another app, Make shortens it with Cuttly and adds a tag to it.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app where your links appear first, such as a spreadsheet or a form, because Cuttly cannot start a scenario itself.

  2. 02

    Add Shorten an URL

    Click the + on the right of the first module, search for Cuttly and choose Shorten an URL. Select your connection, then map the long link coming from the previous module.

  3. 03

    Tag the new short link

    Add Create a tag after it. Map the short link returned by the previous module and write the tag you want, the campaign name for instance, so the link is easy to find in Cuttly.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received (a bundle is one item passed along, here one link). Check that the short link came back.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set the schedule, which is every 15 minutes by default, then switch the scenario on. Each module run counts as one operation on your Make plan.

Modules

What the Cuttly modules do

Cuttly gives you 9 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Cuttly1

Create a tag

Action

In MakeSets a tag for your short URL.

Puts a label on one of your short links so it sits with the right campaign or client in Cuttly. It saves you from sorting links by hand after the fact.

When to use it
right after Shorten an URL, to tag every fresh link with the name of the campaign that produced it.
Watch out
the module works on one link per run, so each tagged link costs one operation.
Cuttly2

Delete an URL

Action

In MakeDeletes your short URL.

Removes a short link from your Cuttly account entirely. Use it to clean up links that should no longer exist, for example after a promotion is over or a page is withdrawn.

When to use it
when a record is closed or archived in another app and its link must disappear too.
Watch out
anyone who clicks the link afterwards hits a dead end, so test on a throwaway link with Run once first.
Cuttly3

Get an URL Analytics

Action

In MakeGets statistic information about your shortened URL.

Fetches the statistics Cuttly holds for a short link and hands them to the next module. That way click data lands in a sheet, a report or a message without opening the Cuttly dashboard.

When to use it
when a campaign ends and the team wants its link results copied next to the rest of the reporting.
Watch out
run it on a schedule or from another app, since Cuttly cannot trigger the scenario.
Cuttly4

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Opens the rest of the Cuttly API to your scenario, reusing the same connection. It covers what the 8 other modules leave out, as long as you know which endpoint you need.

When to use it
only when no listed module does the job; the dedicated modules are simpler to fill in.
Watch out
you write the request yourself, so keep the Cuttly API documentation open next to Make.
Cuttly5

Shorten an URL

Action

In MakeReturns a shortened URL.

Takes a long link and gives you back its Cuttly short version, ready to reuse in the following modules. This is the module most scenarios start their Cuttly part with.

When to use it
each time another app produces a link you plan to share, such as a new article, product page or signup form.
Watch out
map the link from the previous module instead of typing it, or every run shortens the same address.
Cuttly6

Update Source URL

Action

In MakeChanges source URL of your short URL.

Changes where an existing short link leads, while the short link itself stays the same. Printed flyers, emails already sent and social posts keep working after the move.

When to use it
when a landing page gets a new address and dozens of places already share the old short link.
Watch out
anyone clicking afterwards lands on the new page, so double check the destination before the scenario runs.
Cuttly7

Update Unique Clicks

Action

In MakeToggles unique clicks for your short URL.

Switches unique click counting on or off for one short link. It decides whether Cuttly counts every click or each visitor once, which changes how your statistics read.

When to use it
when you tag links for a campaign and want the same counting rule applied to all of them.
Watch out
it is a toggle, so running it twice on the same link puts the setting back where it started.
Cuttly8

Update URL Expiration

Action

In MakeToggles URL expiration for your short URL.

Turns the expiration setting of a short link on or off, so a link can stop working once an offer is over instead of living forever.

When to use it
when an event or a limited offer is marked as finished in another app and its link should close too.
Watch out
Make's documentation does not detail the expiry options, so check the result in Cuttly after your Run once test.
Cuttly9

Update UTM

Action

In MakeChanges your shortened URL's UTM.

Rewrites the UTM parameters attached to a short link, so traffic shows up under the right source and campaign in your analytics tool without creating a new link.

When to use it
when a campaign is renamed or a link gets reused for another channel.
Watch out
check the new parameters in Cuttly after a Run once test, before the link goes back into your campaigns.
Need help

Need help automating Cuttly with Make?

A person reads every message.

FAQ

Questions about the Cuttly Make integration

01Is the Cuttly Make integration free?
Yes, on the Make side. Cuttly is a standard app, available from the Free plan. That plan allows 2 active scenarios, runs no more often than every 15 minutes, and stops an execution after 5 minutes. Paid plans bring the interval down to 1 minute and remove the cap on active scenarios. You still need a Cuttly account with an API key; its own subscription is set on the Cuttly side. Enterprise apps are the exception, since they need the Enterprise plan, but Cuttly is not one of them.
02What do you need to connect Cuttly to Make?
An active Cuttly account and its API key. In Cuttly, open the Edit Account page, generate the key and copy it. In Make, add a Cuttly module, click Create a connection, optionally name it, and paste the key. The connection is then shared by every Cuttly module of your scenarios, so this setup happens only once per account. If Make rejects the key, generate a fresh one on the Edit Account page and paste it into the connection again.
03Does the Cuttly Make integration react in real time?
No, because Cuttly has no trigger in Make: all 9 modules are actions. A scenario therefore starts from another app's trigger, such as a new form entry or a new row, or from a schedule on the first module, every 15 minutes by default. The Cuttly modules then run as soon as that first step hands them a bundle. Before switching the scenario on, click Run once to check that the Cuttly modules receive the link you expect from that first step.
04What if a Cuttly module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the Cuttly API from your scenario with the same connection, which covers what the listed modules do not. You write the request yourself, so keep the Cuttly API documentation open. Also note that the Make documentation for Cuttly is marked as AI generated, so verify important details with Cuttly directly. Test each custom request with Run once and read the bundle Make returns before you let the scenario run on its schedule.
05Should you use Make or n8n for Cuttly?
It depends on the tool your team already runs. In Make, Cuttly offers 9 modules to shorten, tag, update and measure links, plus Make an API Call for the rest, and it works from the Free plan. The same app often has an n8n node too. Pick the platform where your other automations already live, so your link workflows stay next to them. Whichever you choose, Cuttly still needs its API key, and the connection steps above stay the same in Make.