Convertmax Documentation
Talk to us Get started
Guides

Webhook Pipeline

Understand how Convertmax receives webhooks, prevents duplicates, and sends events to downstream tools.

Copy page
Open in ChatGPT Open with page context Open in Claude Open with page context

Use the webhook pipeline when you want Convertmax to receive events from external tools or send events into other systems such as Zapier or other webhook endpoints.

What the pipeline supports

Inbound sources:

  • webhook
  • segment

Outbound destinations:

  • zapier
  • webhook

High-level flow

Inbound
External system
  -> POST /ingest/inbound/:sourceConfigId
  -> verify request
  -> standardize the event
  -> check event volume limits
  -> queue accepted events
  -> skip duplicates
  -> archive and log the result

Outbound
Convertmax event
  -> POST /ingest/outbound
  -> queue
  -> route by destination
  -> deliver to the connected tool

Inbound behavior

Convertmax currently accepts inbound webhook traffic through:

  • POST /ingest/inbound/:sourceConfigId

The sourceConfigId tells Convertmax which saved webhook setup to use for the request. That setup controls how the request is authenticated and how the event is interpreted.

Authentication

Depending on the source type, Convertmax supports:

  • bearer-token authentication
  • optional HMAC signature verification for webhook requests

Volume protection

Inbound webhook traffic is checked before it enters the queue so one source cannot overload processing.

This protection:

  • counts accepted inbound events, not just HTTP requests
  • applies one unit per normalized event
  • treats Segment batch payloads as one unit per item in the batch
  • still returns HTTP 200 for webhook requests
  • manages volume behind the scenes so processing stays stable

Duplicate handling

Convertmax checks for duplicates after an event is queued. If the same inbound event is seen again for the same webhook setup, it is skipped instead of being processed twice.

This protects against:

  • provider retries
  • queue redelivery
  • repeated submissions of the same event identifier

Outbound behavior

Convertmax currently sends outbound events to these destination types:

  • Zapier webhooks
  • generic webhook endpoints

Outbound events are queued first, then delivered in order for each destination so delivery stays reliable.