Resources · Make integration

linkish.io Make integrationAutomate linkish.io with Make.

Can Make send links into linkish.io for you? The linkish.io Make integration gives you 2 action modules, Save a Link and Make an API Call. This page is for people new to Make: connect your account, then build a first scenario that files links from another app.

Try the linkish.io integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the linkish.io Make integration do?

The linkish.io Make integration lets a Make scenario, the automation you build in Make, act on your linkish.io account without code. It offers two action modules: Save a Link, which adds a link to linkish.io, and Make an API Call, which reaches the rest of the linkish.io API with the same connection. It has no trigger, so another app or a schedule starts the flow.

Collect links shared by your team. When a colleague posts a URL in a chat or a form tool, a module from that app hands the link to Save a Link. Nobody has to copy it by hand, and the link lands in linkish.io the moment the scenario runs.

Keep form answers that contain a link. A form app such as the one described on the 123FormBuilder Make integration page can feed its submissions into the scenario, and Save a Link keeps the URL each person sent.

Go beyond the listed module. Make an API Call covers anything the linkish.io API allows that Save a Link does not. You write the request yourself, which asks for a look at the API reference first.

Know the limits before you start. The Make documentation for linkish.io is short: Make itself states that there is not enough public information about the app to document it fully, so field names and behaviors are learned inside the editor. The same app may also exist as an n8n node; the n8n vs Make comparison lays out how the two tools differ. For hands-on help, the Make training starts from the basics.

Connect

How do you connect linkish.io to Make?

  1. 01

    Add a linkish.io module

    In your scenario, click the + and search for linkish.io, then pick Save a Link. The first time, Make asks for a connection, which is your linkish.io account linked to Make once and reused by every linkish.io module. Click Create a connection.

  2. 02

    Name the connection

    This step is optional, but a clear name such as your workspace or your email helps when you run several linkish.io accounts in the same Make organization. Leave the default name if you only have one account.

  3. 03

    Authorize and save

    Depending on what linkish.io asks, either approve access on the linkish.io page that opens, or paste the key the app gives you. Then click Save. The connection now appears in the module and in every other linkish.io module you add.

First scenario

Build your first linkish.io scenario

GoalWhen another app hands over a link, Make saves it to linkish.io with Save a Link.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Since linkish.io has no trigger, this first module comes from the app where your links appear, such as a chat or a form tool.

  2. 02

    Set up the source module

    Search for that app, pick the module that returns new items, and click Create a connection to link your account. Fill its fields; Make lists what it can read once the connection exists.

  3. 03

    Add Save a Link

    Click the + on the right of the first module, search for linkish.io and choose Save a Link. Connect your linkish.io account, then map the URL coming from the previous module into the module fields.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open the bubbles above each module to read the bundles, meaning the items passed along, and check that the right link reached linkish.io.

  5. 05

    Schedule and switch it on

    Click the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. On the Free plan, 15 minutes is also the shortest gap between two scheduled runs.

Modules

What can the linkish.io modules do?

linkish.io gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

linkish.io1

Make an API Call

ActionIn the docs only

This module gives you a direct line to the linkish.io API through the connection you already set up, so any endpoint the API exposes becomes reachable from the scenario. It is the way to cover whatever Save a Link does not handle.

When to use it
choose it once you know the exact API request you need and no listed module does the job.
Watch out
Make documents almost nothing about linkish.io, so the details of the request come from the linkish.io API reference, not from this page.
Need help

Need help automating linkish.io with Make?

A person reads every message.

FAQ

linkish.io and Make: common questions

01Is the linkish.io Make integration free?
Yes, linkish.io is a standard app in Make, so its modules work on the Free plan. That plan has limits worth knowing: 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 and remove the cap on active scenarios. Each module run on one bundle counts as one operation, and operations are what your plan measures.
02What do you need to connect linkish.io to Make?
You need a linkish.io account and a Make account. The Make documentation lists no prerequisite and no specific steps for this app, so the generic flow applies: add a linkish.io module, click Create a connection, give it a name if you like, then authorize Make on the linkish.io page or paste the key the app provides, and click Save. After that, every linkish.io module in your scenarios reuses that same connection without asking again.
03Does the linkish.io Make integration have a real-time trigger?
No, linkish.io has no trigger module in Make, neither scheduled nor instant. A scenario that uses it must start another way. The usual option is a trigger from another app, the tool where your links show up, followed by Save a Link. You can also start on the schedule of the first module, which Make sets to every 15 minutes by default. Whether that other app reacts instantly or on a schedule depends on its own trigger.
04What if a linkish.io module you need is missing in Make?
Use Make an API Call. With it, any endpoint of the linkish.io API can be called from your scenario using the same connection as Save a Link. The catch is documentation: Make states that it cannot fully document linkish.io for lack of public information, so the request details come from the linkish.io API reference. If the API does not offer what you need either, the gap has to be filled by another app in the scenario.
05Should you use Make or n8n for linkish.io?
It depends on the tool your team already runs. On Make, linkish.io offers Save a Link and Make an API Call, which covers saving links and, with some API work, the rest. The same app often exists as an n8n node too. Compare which modules each side offers for your use case, check the connection method in each tool, and pick the platform where the rest of your automations already live rather than splitting them.
Same platform

Other docs you might need on this stack.

Browse all integrations