- Home
- Integrations
- Webhooks
Webhooks
Webhooks to connect your links to your automated scenarios
A link reaches its end date, a page is created or edited: within the minute, TinyLink sends a signed JSON message to the address of your choice. Your Make, Zapier or n8n scenario, or your own server, takes it from there. Up to 10 addresses per workspace, each with its own events; the REST API endpoints work the other way round.
Webhooks included from the Pro plan, at €29 excl. tax a month, no commitment. Free to start, no credit card.
What late information costs you
A private sale ends on Sunday night. The link stops redirecting, as planned, but nobody is told: the campaign stays open in the CRM, the follow-up goes out on Monday for an offer that is over, and the tracking sheet waits for someone to fetch the clicks. Without a signal, your tools work with yesterday’s information, and someone spends their Mondays checking.
The events that matter
Choose, for each address, the events it receives. Each message describes the item concerned, with its IDs and its address, ready to be read by your scenario.
- link.expired: a short link reaches its end date or its maximum number of clicks
- page.created: a page is created in the workspace, from the dashboard, the API or an import
- page.updated: a page or one of its components changes, sent after a minute without further edits
- test.ping: a test message, sent in one click, to check your receiver
Slack, Discord, Teams, Make, n8n and your servers
Paste the address of your Discord, Slack, Microsoft Teams, Google Chat or Telegram channel: the team reads a real message, “The link tnlnk.fr/vente-privee has expired”. Paste a Make, Zapier or n8n scenario, or your own server: it gets the full signed JSON, with the event type in the X-TinyLink-Event header. Nothing to adapt, TinyLink recognises the destination.
Signed, retried, traceable
Each message is signed with HMAC SHA-256 using a secret specific to the address, and timestamped to rule out replays. On failure, TinyLink sends it again up to five times, from one minute to six hours later. The panel shows the history of the last 20 deliveries with their response code; an address that fails 20 times in a row is paused rather than hammered.
A private sale that closes itself
A brand schedules its private sale link until Sunday, 11:59 pm. On the dot, the link stops redirecting and TinyLink sends link.expired to the marketing team’s n8n scenario. Within the minute, the scenario tells the team, closes the campaign in the CRM and copies the final click count into the tracking sheet. Nobody had to think about it.
Frequently asked questions
Which plan includes webhooks?
Webhooks are included from the Pro plan, at €29 excl. tax a month, no commitment, like the API. Each workspace can declare up to 10 addresses, each with its own events.
How do I check that a message really comes from TinyLink?
Each message carries the X-TinyLink-Signature header, with a timestamp and an HMAC SHA-256 signature computed with the address’s secret. Your receiver computes the signature again and compares; the documentation walks through the check step by step. The secret can be renewed at any time.
Do I need to know how to code?
Not with Make, Zapier or n8n: add a webhook trigger to your scenario, copy its address into TinyLink, then send a test message so the tool learns the message structure.
What happens if my scenario is down?
Your receiver must answer with a 2xx code within ten seconds. Otherwise, the message is sent again after 1 minute, 5 minutes, 30 minutes, 2 hours then 6 hours. After 20 failures in a row, the address is paused: fix it, then turn it back on in the panel, which shows the last 20 deliveries and their response.
Your tools notified when it matters
Create your account, move to the Pro plan and add your first address in Library ▸ Integrations ▸ Webhooks. The test message goes out in one click.