Any HTTP Integration

Send webhooks to any HTTP endpoint that accepts POST requests. The HTTP (Webhook) destination is the generic catch-all — use it for any service that doesn't have a dedicated destination type.

Setup

  1. Create an HTTP destination in WebhookLane
    Go to Destinations → Create destination, choose type Webhook, and configure:
    • URL: The full endpoint URL (e.g., https://api.example.com/webhooks)
    • Headers (optional): Add custom headers for authentication or other purposes
  2. Create a route
    Go to Routes → Create route, select your source and the HTTP destination. Optionally add filters and a transform template.

Custom Headers

Add headers for authentication or to pass metadata to the receiving service. Common examples: 

Authorization: Bearer sk_live_abc123
X-API-Key: my-secret-key
X-Custom-Header: custom-value

Headers are sent alongside the default Content-Type: application/json header on every delivery.

Example Transform

Reshape an incoming payload before forwarding it to another service:

{
  "event_type": "{{type}}",
  "source": "webhooklane",
  "data": {
    "id": "{{id}}",
    "name": "{{slackEscape name}}",
    "status": "{{status}}",
    "metadata": {{json metadata}}
  },
  "timestamp": "{{formatDate createdAt}}"
}

No Transform (Passthrough)

If you don't add a transform template, WebhookLane forwards the original payload as-is to the destination. This is useful for simple webhook relaying or fan-out scenarios.

Tips

  • HTTP destinations have a 10-second timeout. If the target endpoint doesn't respond within 10 seconds, the delivery is marked as failed and retried.
  • The Content-Type header is always set to application/json. Custom headers you add are merged with this default.
  • Failed deliveries are retried automatically with exponential backoff.
  • Use the json helper to embed nested objects without escaping: {{json someObject}}.
  • The destination URL must be a full, absolute URL including the protocol (https://).