Resources · Make integration

kutt Make integrationAutomate kutt with Make.

Tired of shortening links by hand, one tab at a time? The kutt Make integration gives you 8 modules: 7 actions and 1 search, all about links and domains. This page shows you how to connect your account and build a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the kutt Make integration do for you?

The kutt Make integration lets Make create, read, change and delete your kutt links and domains for you. You build a scenario (the automation itself, a chain of bricks called modules), and Make runs it on a schedule or when another app hands it new data.

Short links that appear on their own. A new product goes live in your store, a new post is published, a new row lands in a sheet: Create a Link turns that URL into a kutt link and the next module writes it wherever your team needs it.

Campaign links you can fix after the fact. A landing page moves? Update a Link points the existing short link to the new address, so the flyers already printed keep working. Get a Link and List Links pull the details back into a report.

A tidy account. Delete a Link and Delete a Domain remove what a finished campaign left behind, and Create a Domain adds a branded domain when a new brand starts.

Know the limits before you start: kutt has no trigger in Make, so something else has to start the scenario, and Make itself says its documentation for kutt is limited for lack of public information. When a listed module falls short, Make an API Call reaches the rest of the kutt API. New to the tool? Our Make review and the Make training cover the basics, and n8n vs Make helps if you are still choosing.

Connect

How do you connect kutt to Make?

  1. 01

    Add a kutt module

    Open your scenario, click the +, type kutt and pick any module, Create a Link for example. In the connection field, click Create a connection. A connection is your kutt account linked to Make once, then reused by every kutt module.

  2. 02

    Name it and authorize Make

    Give the connection a name if you like, such as the brand it serves. Then follow what the window asks: either authorize Make on the kutt page, or paste the key that kutt gives you. Make does not document which one applies here.

  3. 03

    Save and check the fields

    Click Save. Back in the module, Make can now read what your account holds and fill in the lists it offers. If a list stays empty, the connection is the first thing to recheck.

First scenario

Your first scenario with kutt

GoalWhen a new URL arrives from another app, Make turns it into a kutt short link and hands it back.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the app that holds your long URLs first, a sheet or a form, and its trigger.

  2. 02

    Add Create a Link

    Click the + on the right of that first module, search kutt and choose Create a Link. Use Create a connection if your account is not linked yet.

  3. 03

    Map the long URL

    In the target field, map the URL coming from the first module instead of typing one. Each bundle (one item passed along, here one row) becomes one short link.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time; open the bubble above Create a Link to read what kutt sent back and check that the short link is there.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default) and switch the scenario on. Every module run counts as one operation on your Make plan.

Modules

What each kutt module does

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

kutt1

Create a Domain

Action

In Make“Creates a new domain.”

Adds a new domain to your kutt account from inside a scenario, so a fresh brand or client gets its own address for short links without a trip to the kutt dashboard.

When to use it
a new client record is created in your CRM and that client needs branded links from day one.
Watch out
Make lists no domain settings for kutt, so run it once and read the returned bundle before relying on it.
kutt3

Delete a Domain

Action

In Make“Deletes an existing domain.”

Removes a domain from your kutt account, which keeps the list short once a brand or a client relationship ends.

When to use it
a client is marked as lost in your CRM and their branded domain should go with them.
Watch out
treat every delete as final. Put a filter in front of this module and test it on a spare domain before you point it at a real one.
kutt6

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any endpoint of the kutt API with the connection you already set up, which is how you cover a need the seven other modules do not reach.

When to use it
the kutt API offers something you need and no listed module does it.
Watch out
you write the request yourself here, so keep the kutt API reference open and test the call with Run once before adding modules after it.
Need help

Need help automating kutt with Make?

A person reads every message.

FAQ

Questions people ask about kutt and Make

01Is the kutt Make integration free?
Yes. kutt is a standard app in Make, so its modules work from the Free plan. That plan has real limits though: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Make counts usage in operations, one per module run, and the Make pricing page gives the details of each plan.
02What do you need to connect kutt to Make?
A kutt account and a Make account. Make's documentation lists no special prerequisite for kutt. You add any kutt module, click Create a connection, name it if you want, then either authorize Make on the kutt page or paste the key kutt gives you, depending on what the window asks, and click Save. The connection is stored once and every kutt module in every scenario can reuse it, so you do this step a single time per kutt account you want to automate.
03Can a kutt scenario start on its own in Make?
Not from kutt itself. The kutt app has no trigger in Make, only 7 actions and 1 search, so kutt cannot tell Make that something happened. Two ways around it work well. You can put the trigger of another app first, like a new form entry or a new sheet row, and let the kutt modules follow. Or you can start with a kutt module and let the scenario run on its schedule, every 15 minutes by default, and down to 1 minute on a paid plan.
04What if a kutt module is missing in Make?
Use Make an API Call. It is the eighth kutt module, and it calls any endpoint of the kutt API with the connection you already created, so you are not stuck with the seven other modules. Keep in mind that Make says its own documentation for kutt is limited, because little public information about the app exists. Test every new module or API call with Run once and read the bundles it returns before you switch the scenario on.
05Make or n8n for kutt?
It depends on how your team likes to build. On Make, kutt comes with 8 modules covering links and domains, plus the API call module for everything else, and you build visually by chaining modules in the editor. n8n often has a node for the same app, so check its catalog before deciding. Compare the two on the modules each one offers for kutt and on the way your team prefers to work, rather than on a general ranking of the tools.