Platform · webhooks

Events pushed
to your systems.

Signed event notifications with configurable retries and a full delivery history.

Permission first. Every brand distinct.
Why it matters

Fire-and-forget is not integration.

A webhook that posts once and gives up turns every deploy, timeout, and transient 500 into permanently lost data. Worse, without signatures the receiving endpoint has no way to know the payload is genuinely from you.

SendNectar signs every outbound delivery, retries on a configurable attempt budget, and records each attempt with its response status — so an integration failure is visible and recoverable rather than invisible and permanent.

Capabilities

Outbound webhooks, in detail.

01

Signed deliveries

Each webhook has a stored secret, and deliveries are signed so your endpoint can verify the payload actually came from SendNectar.

02

Subscribe by event type

Choose exactly which event types an endpoint receives instead of accepting the entire firehose.

03

Configurable timeout

Set the request timeout per webhook — the default is five seconds — to match what your endpoint can actually promise.

04

Retry budget

Set maximum attempts per webhook, defaulting to five, so transient failures resolve themselves without manual replay.

05

Full delivery history

Every attempt records the webhook, event type, status, response status code, and time — debugging is a query, not a support ticket.

06

Secrets never returned

Webhook secrets are submitted to a dedicated endpoint and encrypted server-side. They are never returned by the API or bundled into browser code.

The product surface

Webhook configuration.

Defaults chosen to be safe; every one of them adjustable.

endpoint_url
Where deliveries are posted
event_types
The explicit set of events this endpoint receives
timeout_ms
Per-request timeout — defaults to 5,000
max_attempts
Retry budget per delivery — defaults to 5
Secret
Stored encrypted and referenced by ID; used to sign deliveries
Delivery record
Event type, status, response status, and created-at per attempt

Bring your provider.
Keep your brands distinct.
Start today.

Set up your first workspace, connect a provider, and publish a workflow — free, in test mode, before you pay a thing.