How to Use Webhooks in UniLink (Send Real-Time Events to External Services)

Automatically notify your CRM, automation tool, or custom server the moment someone subscribes, submits a form, or places an order on your UniLink page.

A webhook is a push notification sent from UniLink to a URL you control. Instead of polling your dashboard every hour to check for new subscribers or orders, you configure a webhook once and UniLink calls your endpoint automatically every time a relevant event happens. This is how UniLink connects to CRMs, internal databases, Slack channels, and custom automation servers in real time — without needing a Zapier intermediary.

What Webhooks Does

When a trigger event occurs on your page — a new email subscriber, a form submission, a product order, a chatbot conversation — UniLink sends an HTTP POST request to your specified endpoint URL. The request body is a JSON object describing what happened: the event type, a timestamp, and the relevant data (subscriber email, form fields, order amount, etc.).

You can create multiple webhooks, each listening for different events and pointing to different endpoints. For example, one webhook can send new orders to your fulfillment system and another can send new subscribers to your email marketing API. Each webhook has its own delivery log so you can see every request that was sent, the HTTP response your server returned, and whether delivery succeeded or failed.

Failed deliveries are retried automatically up to three times with exponential backoff. If all retries fail, the webhook is marked as failed in the log and you can trigger a manual retry from the dashboard.

How to Get Started With Webhooks

1. Open Integrations in your Dashboard — log in, go to Settings or the Integrations section, and select Webhooks.
2. Click Add Webhook — this opens the webhook creation form.
3. Enter your endpoint URL — this is the URL on your server or third-party service that will receive the POST request. It must be publicly accessible over HTTPS. For testing, you can use a free service like Webhook.site to inspect incoming requests without any server setup.
4. Select the event types you want to receive — check all events relevant to your use case: New Subscriber, Form Submission, New Order, Chatbot Lead, or Link Click. You can select multiple events for one endpoint or create separate webhooks per event type.
5. Add a secret key (optional but recommended) — UniLink will include this key in each request header as X-UniLink-Signature. Your server can verify the signature to confirm the request is genuinely from UniLink and not from a third party spoofing the payload.
6. Send a test event — click Send Test to fire a sample payload to your endpoint. Check your server logs or Webhook.site to confirm the request arrived and your server responded with HTTP 200.
7. Save the webhook — once the test succeeds, save. UniLink will begin delivering live events immediately.

How to Use Webhooks

1. Read the delivery log — open any webhook and click Delivery Log. Each row shows the event, the timestamp, your server's HTTP response code, and the response body. A green checkmark means delivery succeeded; a red X means it failed.
2. Retry a failed delivery — click Retry next to any failed entry. UniLink resends the original payload. This is useful if your server was temporarily down and you want to reprocess missed events.
3. Inspect the payload — click any log entry to see the full JSON body that was sent. Use this to map field names when setting up your server-side handler or a Zapier Catch Hook.
4. Pause a webhook without deleting it — toggle the Active switch off. UniLink stops sending events but retains the configuration and delivery history. Toggle back on to resume.
5. Edit event subscriptions — return to the webhook settings at any time to add or remove event types without recreating the webhook.
6. Monitor error rates — if your server consistently returns 4xx or 5xx responses, check the delivery log for patterns. A 400 error usually means a payload parsing issue on your server; a 401 or 403 means your endpoint requires authentication that UniLink is not providing.
7. Delete old webhooks — remove webhooks for endpoints you no longer use to keep the list clean and avoid sending data to inactive URLs.

Key Settings Explained

How to Get the Most Out of Webhooks

The most powerful use of UniLink webhooks is syncing new subscribers to an external email marketing tool or CRM. When a visitor enters their email in a Subscribe block, the webhook fires within seconds. Your server receives the email, first name, and any custom fields, and can immediately add the contact to Mailchimp, ActiveCampaign, HubSpot, or any system with an API — without manual exports.

For e-commerce use cases, hook the New Order event to a fulfillment webhook. When an order is placed on your UniLink storefront, the webhook sends the order data — items, quantity, shipping address — to your fulfillment partner or warehouse system in real time. This eliminates the delay of checking the UniLink dashboard manually and reduces the risk of missed orders during busy periods.

If you build your own server, make sure your endpoint responds with HTTP 200 within five seconds. UniLink considers any response outside that window a failure and will retry. A slow handler that takes ten seconds to process an order will cause unnecessary retries and duplicate entries in your system. Respond 200 immediately, then process the payload asynchronously.

Use the delivery log as a debugging tool during setup, not just when things break. Reviewing the first five live payloads after launch confirms that field names match what your code expects and that no events are being silently dropped.

Troubleshooting Common Issues