Webhooks: Get Real-Time Link Event Notifications
⚠️ Coming Soon — Webhook management is not yet available in the dashboard or API. This page describes the planned feature. We’ll update this guide when it launches.
Brevr webhooks send a real-time notification to a URL you control every time something happens in your account — a click, a new link, or a change. Your tools react instantly without you lifting a finger.
What You’ll Learn
- What webhooks do and when to use them
- Which events Brevr can notify you about
- How to set up a webhook in a few steps
- How to confirm notifications are genuinely from Brevr
- What happens if your receiving URL is temporarily unavailable
What Webhooks Do
A webhook is an automatic notification. When an event happens in Brevr, Brevr immediately sends the details to a URL you specify — no waiting, no checking, no manual export. Your receiving URL can be a no-code tool like Zapier or Make, a Slack integration, your CRM, or a custom system your team built.
📸 Screenshot: [Settings → Webhooks page showing an active webhook with its URL and status]
Think of it like a text message alert. Instead of you checking Brevr for updates, Brevr messages your tool the moment something happens.
Supported Events
Brevr fires a notification for these four events.
| Event | When It Fires | What It Tells You |
|---|---|---|
link.clicked | Every time someone clicks one of your links | Which link was clicked, when, and basic visitor context |
link.created | When a new link is added to your workspace | The new link’s details — short code, destination, tags |
link.updated | When a link’s settings are changed | Which link changed and what the new settings are |
link.deleted | When a link is removed from your workspace | Which link was deleted and when |
You can choose to receive all events or only the ones you need.
How to Set Up a Webhook
📸 Screenshot: [Webhook creation form with URL field and event checkboxes]
- Go to Settings in your Brevr sidebar.
- Click Webhooks.
- Click Add Webhook.
- Paste the URL where you want Brevr to send notifications. This is provided by your receiving tool (Zapier, Make, your own system, etc.).
- Select which events you want to receive notifications for. You can choose one, several, or all four.
- Click Save.
Brevr immediately sends a test notification to confirm your URL is reachable. Check your receiving tool for the test event.
📸 Screenshot: [Webhook list showing status “Active” with a green indicator]
Verifying Notifications Are From Brevr
Anyone who knows your receiving URL could theoretically send fake notifications to it. To protect you, Brevr includes a security code with every notification it sends. Your receiving system can check this code to confirm the notification genuinely came from Brevr and was not tampered with.
📸 Screenshot: [Webhook detail page showing the security code / secret value]
When you create a webhook, Brevr gives you a secret value. Your developer or no-code tool uses this value to verify each incoming notification. Most webhook-friendly tools (Zapier, Make, n8n) handle this verification step automatically once you paste in your secret.
If you do not verify incoming notifications, your system may still work — but it will be open to spoofed data. We recommend verifying whenever possible.
What Happens If Your Receiving URL Is Unavailable
If Brevr sends a notification and your receiving URL does not respond — because your server is restarting, your no-code tool is paused, or there is a temporary outage — Brevr does not give up.
📸 Screenshot: [Webhook delivery log showing a failed attempt and retry queue]
Brevr automatically retries failed notifications over the next several hours. If your URL comes back online within that window, the notification will eventually get through. If it never responds, the notification is dropped after the final retry.
You can view the delivery log for any webhook in Settings → Webhooks. The log shows each attempt, its status (delivered or failed), and the time of each retry.
Plan Limits
The number of active webhooks you can have at one time depends on your plan.
| Plan | Active Webhooks |
|---|---|
| Free | 1 |
| Pro | 5 |
| Business | Unlimited |
If you reach your limit, delete an existing webhook before adding a new one.
Frequently Asked Questions
Do I need a developer to use webhooks?
Not always. No-code tools like Zapier, Make, and n8n can receive Brevr webhook notifications and connect them to hundreds of other apps — no code required. You just paste your receiving URL from those tools into Brevr. A developer is only needed if you want to build a custom receiving system.
Can I receive notifications for only specific links, not all of them?
Currently, webhooks apply to your entire workspace. All link.clicked events for all links in the workspace will be sent to your receiving URL. You can filter by link on the receiving end using the data included in each notification.
How quickly does a webhook notification arrive after an event?
Brevr sends notifications within a few seconds of the event. Delivery time from there depends on your receiving URL’s response speed and any processing your tool does.
Can I pause a webhook without deleting it?
Yes. In Settings → Webhooks, toggle the webhook to inactive. Brevr will stop sending notifications until you reactivate it. Your webhook configuration is preserved.
Watch the Full Walkthrough
🎬 Video walkthrough: [Setting Up Your First Brevr Webhook — ~2 min]
Walk through every step below with the screenshots to follow along at your own pace.
Step 1: Open Webhooks in Settings
Click Settings in your Brevr sidebar, then click Webhooks to open the webhook management page.
📸 Screenshot: [Brevr Settings page with the Webhooks section selected in the left navigation, showing an empty webhook list with an “Add Webhook” button]
Step 2: Click Add Webhook and Paste Your Receiving URL
Click Add Webhook to open the creation form. Paste the URL that your receiving tool — Zapier, Make, n8n, or your own server — gave you. This is the address Brevr will POST notifications to.
📸 Screenshot: [Webhook creation form with the URL field filled in and the cursor positioned in it]
Step 3: Select the Events You Want to Receive
Check the boxes for the events that matter to your workflow. You can choose one or all four: link.clicked, link.created, link.updated, and link.deleted.
📸 Screenshot: [Webhook form with the event checkboxes visible — link.clicked checked, others unchecked — illustrating selective subscription]
Step 4: Save and Confirm the Test Notification
Click Save. Brevr immediately fires a test notification to your receiving URL. Switch to your receiving tool and confirm the test event arrived.
📸 Screenshot: [Webhook list showing the newly created webhook with a green “Active” status indicator]
Step 5: Copy Your Webhook Secret for Verification
Open the webhook detail view and copy the secret value Brevr generated. Paste it into your receiving tool’s verification setting. This lets your tool confirm every notification genuinely came from Brevr.
📸 Screenshot: [Webhook detail page showing the secret value field with a “Copy” button beside it]
Step 6: Check the Delivery Log
After your next real event fires, open the webhook delivery log in Settings → Webhooks. Confirm the notification shows as delivered. If it failed, the log shows the retry schedule so you know when to expect it.
Next Steps
- REST API — Create and manage links programmatically from your own systems.
- Retargeting Pixels — Build ad audiences from everyone who clicks your links.
- Integrations Overview — See all the ways Brevr connects to your tools.