Shorten every new row
A new row in a sheet goes to the API and the short link is written back next to it.
- url
- shorturl
Create short links from any scenario with the HTTP module, and start scenarios the moment a link is created, clicked or stops working.
Make talks to your account in two ways. Use one of them or both in the same scenario.
Add HTTP, Make a request to your scenario and fill it in like this. Turn on Parse response and the short link is ready for the next modules.
POST https://minzo.link/usethisapi/url/add
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json
{
"url": "https://www.example.com/summer-sale",
"custom": "summer"
}
{
"error": 0,
"id": 1042,
"shorturl": "https://minzo.link/summer"
} Start the scenario with Webhooks, Custom webhook. Add its address on your Webhooks page and choose the events it should receive.
X-Nobiscum-Signature: 9f2c…e41a
{
"shorturl": "https://minzo.link/summer",
"longurl": "https://www.example.com/summer-sale",
"code": 404,
"event": "link.broken",
"date": "2026-11-03 19:26:31"
} Each idea uses only the fields the API and the webhooks really send.
A new row in a sheet goes to the API and the short link is written back next to it.
Each new item of a feed gets a short link, then goes to your social or newsletter tool.
When a destination stops working, a message lands in the right Slack channel.
Store each visit with country, city, browser and referrer, then build your own report.
An uptime monitor goes down and everyone on call gets an email.
Every new short link becomes a record your whole team can search.
In your dashboard open Developers, then API keys, and create a key just for Make.
Choose HTTP, Make a request and enter the URL, the POST method and the Authorization header.
Put the address from an earlier module in the url field of the JSON body.
Make shows the response with shorturl, ready to map into the next module.
Create a Custom webhook in Make, add its address on your Webhooks page and send a test.
Create an API key just for Make. If you ever revoke it, your other apps keep working.
Every webhook carries an X-Nobiscum-Signature header, an HMAC SHA-256 of the body made with your webhook secret.
Send a test event from the Webhooks page so Make learns the data structure before the first real event.
Webhook addresses on private or internal networks are refused, when you save them and again before each delivery.
The click event fires on every visit. Pick it only when you need it, or add a filter in your scenario.
Events are queued and delivered in the background, so your visitors never wait for Make.
How the API and the webhooks work with your Make scenarios.
No. The built-in HTTP module creates short links through our API, and the built-in Webhooks module receives events. Both come with every Make account.
Create short links with a custom alias, domain, tags, password or expiry date. The response returns the new short link so the next modules can use it.
A link is created, a link is clicked, a link destination stops working, and an uptime monitor goes down or comes back up. You choose the events for each webhook address.
They are queued and delivered in the background within moments, so your short links never wait. Each event is sent once.
Each request carries an X-Nobiscum-Signature header. Compute an HMAC SHA-256 of the body with your webhook secret and compare the two.
Links created through the API count toward the link limit of your plan, and the API applies a rate limit per account.
Create an API key, add one HTTP module, and every scenario you build can make and track short links.