Generic HTTP destination

Nimriz provides a Generic HTTP outbound destination that sends server-side click and conversion events to any URL. This is perfect for custom data pipelines, proprietary systems, or niche automation platforms like Make (Integromat).

Configuration

To set up a Generic HTTP destination, you configure the connection details similarly to a standard webhook, but with extra control over the payload shape.

1. HTTP Request Setup

1. In Nimriz, go to Settings → Integrations → Outbound Destinations.
2. Click Add destination and choose Generic HTTP.
3. Enter your Endpoint URL.
4. Set your HTTP Method (usually POST).
5. (Optional) Provide custom headers, such as Authorization: Bearer <your-token>.

2. Payload Templating

By default, Nimriz sends the full canonical JSON event schema. If your receiving system requires a specific structure, you can construct a Payload Template.

Nimriz uses a simple variable substitution engine. Wrap variable names in double curly braces {{variable_name}} inside your JSON template.

Example Template:

{
  "event_time": "{{timestamp}}",
  "link": "{{short_url}}",
  "device_type": "{{device_category}}",
  "source": "{{utm_source}}"
}

The system will interpolate the fields from the Nimriz click event payload before executing the HTTP request.

Rate Limiting and Delivery

The generic HTTP connector respects the same async delivery semantics as all destinations. Events are queued, rate-limited, and sent with automatic retry backoffs if your endpoint returns a temporary error (like 429 or 5xx). You can monitor delivery health and dead-letter items from the Destination settings.