Channels

Trigger any external system at any point in your lifecycle workflow

Custom JSON payloads, auth headers, and automatic retry, on any campaign or journey event.

Book a call

Trusted by lifecycle teams at

Triggers

Trigger anything, anywhere

Any lifecycle event can fire a webhook to any endpoint that accepts an HTTP POST.

Any trigger event

Send, open, click, bounce, journey entry, step completion, journey exit, goal reached, or audience entry.

Custom JSON payload

Define exactly what data is included: user profile fields, event properties, campaign identifiers, or any value Sortment has at trigger time.

Auth headers

Configure Bearer tokens, API keys, or any custom header your endpoint requires.

Trigger:  Goal reached
Endpoint: https://example.com/hooks/lead
Auth:     Bearer ••••••••••••

Reliability

Reliable delivery, even when endpoints fail

Automatic retry with exponential backoff, so no events are lost while an endpoint is down.

Automatic retry

If the endpoint errors or times out, Sortment retries delivery automatically.

Exponential backoff

Retry intervals increase over time to avoid overwhelming a recovering endpoint.

Delivery logs

Every call is logged with its timestamp, payload, HTTP response code and status.

“We got an uplift of four to five times just by using Sortment on a daily basis, understanding which leads to call.”

— Akshat Saxena, Co-founder, Kinetic Age

Read full case study

Capabilities

Everything webhooks can do

The full capability set: triggers, payloads and reliable delivery.

Triggers

Any campaign or journey event	✓
Journey exit	✓
Goal reached	✓
Audience entry	✓
Multiple webhooks per workflow	✓

Payload & Auth

Custom JSON — any structure	✓
Bearer token	✓
API key	✓
Custom auth headers	✓

Reliability

Automatic retry on failure	✓
Exponential backoff	✓
Configurable retry limit	✓
Delivery logs with response codes	✓

Compatibility

Works with any HTTP endpoint

✓

FAQs

What events can trigger a webhook?

Any campaign or journey event: sent, delivered, opened, clicked, bounced, unsubscribed, journey entered, step completed, journey exited, goal reached, audience entry.

Can I include custom data in the payload?

Yes. Define the payload structure yourself — include any user profile field, event property, campaign metadata, or static value Sortment has at trigger time.

What happens if my endpoint is down?

Sortment retries automatically with exponential backoff. Inspect the delivery log to see what failed, when, and whether it recovered.

Can I fire multiple webhooks in a single journey?

Yes. A journey can include webhook steps at any point — different endpoints, different payloads, different trigger conditions — all within the same workflow.

Is there a payload size limit?

Sortment does not impose a strict limit. Practical limits are set by your receiving endpoint.

Find the growth signals your team is missing.

Book a 30-minute call. See how Sortment turns opportunities into revenue.

Book a call Book a call

No migration · Works alongside your existing stack