Coming soon

Webhooks

Event delivery for your stack is planned.

Interactive product demo

Webhooks

Planned preview

This is a non-operational product preview. It does not save, send, deploy, or call an API.

Webhook delivery concept

This is a non-operational product preview. It does not save, send, deploy, or call an API.

Example data

All people, links, events, and metrics shown here are deterministic example data.

Coming soon

Webhook delivery with retries and signed payloads is on the roadmap.

  • Click, expiry, and health events
  • Retries with signatures
  • On the roadmap

What this feature does

Event delivery for your stack is planned.

Webhooks are not available today. Click, expiry, and health events with signed payloads, retries, and delivery logs are planned.

Use this capability when you need more control than a basic short URL provides.

Implementation and operating details

The workflow stays attached to the short link, so you can manage the destination and its rules without replacing the URL already in circulation.

  • Click, expiry, and health events
  • Retries with signatures
  • On the roadmap

How it works

01

Pick your events

Choose click, expiry, and health events for your links.

02

Connect your system

The planned webhook service will deliver selected events to a destination you control.

03

Automate responses

React to every event in real time — delivery with retries and signatures is on the roadmap.

Operational guide

How DrutoLink processes it

The preview models future event subscriptions, signed payloads, retry policy, and delivery history. Registration, test delivery, signatures, retries, and logs are not available today.

Understand the signals, processing order, fallback, and checks that matter before you rely on this capability.

Required inputs and signals

Configuration input
Webhooks are not available today. Click, expiry, and health events with signed payloads, retries, and delivery logs are planned.
Signals and connected controls
Planned

Decision, fallback, and common mistakes

Do not design production automation around the displayed event names or payload shape. Those details can change before a supported webhook contract ships.

This capability is planned and cannot be used in the current product. The workflow below explains the intended direction, not a feature you can deploy today.

Implementation requirements preview

This capability is not available yet. Use this list to evaluate the planned workflow, not as current product instructions.

  1. 01 Pick your events. Choose click, expiry, and health events for your links.
  2. 02 Connect your system. The planned webhook service will deliver selected events to a destination you control.
  3. 03 Automate responses. React to every event in real time — delivery with retries and signatures is on the roadmap.

Why teams use it

Click, expiry, and health events
Real-time delivery
Retries with signatures (roadmap)
No polling required
Future integrations should verify signatures, respond quickly, process events idempotently, and tolerate duplicate or delayed delivery.

Measurement and reporting

Review click activity and the relevant link, campaign, audience, or variant breakdowns in DrutoLink analytics. Use consistent UTM parameters when results must also be reconciled with destination-side analytics.

What you can evaluate

Click, expiry, and health events · Real-time delivery · Retries with signatures (roadmap)

How to interpret results

A redirect click confirms that the link served a destination. It does not by itself prove a signup, purchase, or qualified visit. Compare the same date range and traffic definition before making a decision.

Current status and limitations

Coming soon

Webhook delivery with retries and signed payloads is on the roadmap.

This capability is planned and cannot be used in the current product. The workflow below explains the intended direction, not a feature you can deploy today.

Important boundary

Use the default destination and documented fallback behavior for cases where a rule cannot be evaluated. Test important links from representative devices and networks before broad distribution.

What events can webhooks listen for? Planned events cover link clicks, expiries, and health changes.

Best use cases

Practical examples

These are common situations where the capability can reduce manual link changes or make reporting easier to understand.

  • 01 Syncing clicks into your CRM
  • 02 Alerting on unhealthy links
  • 03 Automating post-click workflows
  • 04 Notify an incident channel about link-health changes or send supported click and conversion events into an automation workflow.

Is this the right fit?

Choose this feature when

You need one controlled short URL, a repeatable operating workflow, and reporting that stays connected to the link. Click, expiry, and health events

Use another approach when

Your requirement depends on a capability marked partial or planned, requires identity-level certainty, or needs conversion attribution that must be measured in the destination product.

Frequently asked questions

What events can webhooks listen for?

Planned events cover link clicks, expiries, and health changes.

When will webhooks ship?

Webhook delivery with retries and signed payloads is on the roadmap.

Do webhooks replace the API?

Webhooks are not available today. Click, expiry, and health events with signed payloads, retries, and delivery logs are planned.

Build a link that fits the job

Start with the free plan