Send Nimriz events to a generic HTTP endpoint

Deliver link, QR, card, and conversion events to any HTTPS endpoint with custom methods, custom headers, and fully templated JSON payloads.

Read setup docs All integrations

Link clicks
QR scans
Card events
Conversions

Event flow

Async delivery

Link clickQR scanCard eventConversion

Nimrizredact · filter · map

Generic HTTP

Bot traffic is excluded by default. Delivery runs off the redirect path with automatic retries.

Why Generic HTTP with Nimriz

Internal tools rarely accept someone else's payload format. The Generic HTTP destination sends POST, PUT, or PATCH requests with your headers and a body you template field by field, so the receiving service gets exactly the JSON it already parses, not a vendor schema you have to adapt to.

Your payload, not ours

Most link platforms offer a fixed webhook body. Nimriz lets you write the JSON body yourself with {{variable}} substitution from the canonical event, down to field names, nesting, and constants.

Real HTTP semantics

Choose POST, PUT, or PATCH and attach custom headers such as authorization tokens, so the destination treats Nimriz like any first-class internal client.

Delivery you can operate

Temporary failures retry automatically with backoff, persistent failures land in a dead-letter view, and delivery health is visible per destination.

Parse, map, transform

Reshape every event before Generic HTTP sees it.

Template the entire request body. Each {{variable}} is interpolated from the canonical event before the request is sent, so legacy services, internal APIs, and data collectors receive a body they already understand.

Canonical Nimriz event

 1{
 2  "event_type": "link.qr_scanned",
 3  "event_id": "9f4d5dbd-c8b8-4c89-a080-b4f70fce8f53",
 4  "timestamp": "2026-04-13T12: 15: 00.000Z",
 5  "domain_name": "go.brand.com",
 6  "short_code": "spring",
 7  "short_url": "https://go.brand.com/spring",
 8  "touch_type": "qr_scan",
 9  "country": "US",
10  "device_category": "mobile",
11  "browser_family": "Mobile Safari",
12  "referrer_host": "instagram.com",
13  "utm_source": "direct-mail",
14  "utm_medium": "qr",
15  "utm_campaign": "spring-launch",
16  "variant_key": "B"
17}

Action mapping rules

templatebody = your JSON, any {{field}} from the event
static"source": "nimriz" written inline in the template
renamefield names defined by your template keys
excludefields left out of the template are never sent

POST · your endpoint

 1{
 2  "event_time": "2026-04-13T12: 15: 00.000Z",
 3  "event_ref": "9f4d5dbd-c8b8-4c89-a080-b4f70fce8f53",
 4  "link": "https://go.brand.com/spring",
 5  "device_type": "mobile",
 6  "source": "nimriz",
 7  "campaign": "spring-launch"
 8}

The template is configured per action, so one endpoint can receive click events in one shape and conversion events in another.

Under the hood

What Nimriz sends, and how.

Send webhook-style HTTP requests with configurable destination details.

Plan note

Connector access, mapping controls, and event volume depend on plan. Use pricing and setup docs to confirm the right path before configuring production delivery.

Methods: POST, PUT, or PATCH to any HTTPS endpoint you control
Headers: Custom headers per destination, including authorization tokens
Payload: Canonical event JSON by default, or a fully templated custom body
Reliability: Automatic retries with backoff and a dead-letter view for persistent failures
Never forwarded: Raw IP addresses and complete User-Agent strings

Guided setup

Connected in four reviewed steps.

01
Connect
Add credentials in the destination catalog and run Test connection before anything is saved.
02
Filter events
Choose triggering event types and narrow delivery by domain, space, tag, country, or field conditions.
03
Map fields
Start from the default schema, then rename, exclude, pin, or template fields to fit the destination.
04
Review and test
Send a dry-run test event, confirm the payload, then enable the action for live delivery.

Use cases

Custom automation
Internal tools
Data collection endpoints

Privacy notes

Nimriz uses destination-aware payloads and privacy-aware analytics language. Do not send secrets, raw personal data, or provider credentials in public links.

Nimriz never forwards raw IP addresses or complete User-Agent strings in integration payloads. Strict privacy mode omits visitor hashes and selected granular fields such as city.

Analytics privacy docs

Pair Generic HTTP with the rest of the catalog.

Live

Zapier

Trigger Zaps instantly from link, QR, and click activity, and create or update branded links from any of the apps your team already automates with.

Live

Make

Feed link, click, and QR scan events into Make scenarios over instant webhooks, and manage branded links from modules inside the visual builder.

Live

n8n

Use the Nimriz community node to trigger self-hosted or cloud n8n workflows from link activity, and manage branded links with a dedicated operations node.

Live

Webhooks

Receive signed, replayable lifecycle events from Nimriz in your own backend, with HMAC signatures, retry schedules, and a delivery history you can operate.