n8nIntegration

Ready workflows, one import away.

Import a template into n8n Cloud or your own server. One creates short links through the API, the other reacts to link and monitor events from your account.

Get Started Free See how it works
  • Two templates
  • HTTP Request node
  • Webhook trigger
Two templates

What is inside each workflow

Download them from your dashboard and import them with Import from File. Both are plain n8n JSON you can change as you like.

What it does

A manual trigger and an HTTP Request node that sends a long URL to the API. Swap the trigger for your own, like a new form entry, a new row or a new post.

Nodes and fields

Start
Manual trigger, so you can try the workflow right away.
Shorten link
HTTP Request node, POST to the API with your key in the Authorization header.
jsonBody
The long URL in the url field. Map it from an earlier node.
shorturl
Comes back in the output, ready for the next node.
Shorten linkPOST
URL: https://minzo.link/usethisapi/url/add
Authorization: Bearer YOUR_API_KEY
{
  "url": "https://www.example.com"
}
Output200 OK
{
  "error": 0,
  "id": 1042,
  "shorturl": "https://minzo.link/summer"
}

What it does

A Webhook trigger that receives link and monitor events from your account, followed by an empty step where your own nodes go.

Nodes and fields

Webhook
POST trigger with its own path. Copy the Production URL after you activate the workflow.
event
Tells which event happened, for example link.created or monitor.down.
date
When the event happened.
next
Add an If or Switch node to handle each event differently.
POST /webhook/minzo-…200 OK
X-Nobiscum-Signature: 9f2c…e41a
{
  "name": "Main website",
  "url": "https://www.example.com",
  "event": "monitor.down",
  "date": "2026-11-03 19:28:48"
}
Events

Everything your workflow can react to

Choose the events for each webhook address on your Webhooks page.

Link created

Fires when a short link is created in your account.

  • link.created

Link visited

Fires on every click, with country, city, browser and referrer.

  • link.visited

Link destination stopped working

Fires when a link destination fails two checks in a row, at least a day apart.

  • link.broken

Monitor is back up

Fires when a monitored site responds again.

  • monitor.up

Monitor is down

Fires when a monitored site stops responding.

  • monitor.down

Shorten on demand

Not an event: any node can create a short link through the API whenever your workflow needs one.

  • POST /usethisapi/url/add
Ideas

Workflows you can build from the templates

Each idea uses only the fields the API and the webhooks really send.

Shorten links from a form

Every new form entry gets a short link that goes back to the person in the confirmation email.

  • url
  • shorturl

Shorten every new row

Read new rows from a sheet, shorten the link in each one and write the short link back.

  • url
  • shorturl

Route events to the right place

A Switch node sends broken links to Slack and monitor alerts to email.

  • event
  • shorturl
  • code

Keep a click history

Every visit is stored with country, city, browser and referrer in your own database.

  • shorturl
  • country
  • referer

Open a ticket for broken links

When a destination fails twice, a ticket is created with the short link and the error code.

  • shorturl
  • longurl
  • code

Archive new links

Each new short link is saved to a sheet with its destination, for a simple shared list.

  • longurl
  • shorturl
Setup

Running in five steps

  1. 1

    Download a template

    In your dashboard open Integrations, then n8n, and download the workflow you need.

  2. 2

    Import it

    In n8n open a new workflow and use the menu, Import from File.

  3. 3

    Add your API key

    Create a key just for n8n and put it in the Authorization header in place of YOUR_API_KEY.

  4. 4

    Execute the workflow

    Click Execute workflow and check that a short link comes back.

  5. 5

    Connect the events

    Activate the events workflow, copy the Production URL of the Webhook node, add it on your Webhooks page and send a test.

Good to know

Built for your own automation server

Cloud or self-hosted

Both workflows work on n8n Cloud and on your own server. To receive events, your n8n must be reachable from the internet.

Your key stays yours

The template holds a YOUR_API_KEY placeholder, never a real key. Create a separate key for n8n so you can revoke it alone.

Signed requests

Every event carries an X-Nobiscum-Signature header, an HMAC SHA-256 of the body made with your webhook secret. Check it with the Crypto node.

Production URL

The test URL of the Webhook node only listens while you wait for a test. Activate the workflow and use the Production URL.

Sent once

Each event is delivered once. Keep the workflow active so no event is missed while it is off.

Public addresses only

Webhook addresses on private or internal networks are refused, when you save them and again before each delivery.

FAQ

n8n Integration
Frequently Asked Questions

Templates, keys and events for n8n Cloud and self-hosted n8n.

Two templates
Cloud or self-hosted
Signed events

No. The templates use only built-in nodes: Manual Trigger, HTTP Request, Webhook and No Operation.

Yes. Creating links works from any n8n. To receive events, your n8n needs a public address, because webhook addresses on private networks are refused.

In your dashboard under Integrations, then n8n. The events template is there when your plan includes webhooks.

A link is created, a link is clicked, a link destination stops working, and an uptime monitor goes down or comes back up.

Compute an HMAC SHA-256 of the request body with your webhook secret, for example with the Crypto node, and compare it with the X-Nobiscum-Signature header.

Each event is sent once, in the background. Events that arrive while your n8n is down are not sent again, so keep the workflow active.

Plug your links into n8n

Download a template, add your key and your first workflow is running in minutes.

Get Started Free Back to how it works