Help Centre Contact Sales
Sign in
Noxtill
Skip to content

Webhook Automation

Connect the event to the next step.

When another app sends an event, Noxtill checks its signature, ignores duplicates and creates or updates the right record, with every delivery logged.

Source app

Payment providerpayment.succeeded

Payload

Signature verified
{ "event": "payment.succeeded",
  "id": "evt_5Hq2",
  "amount": 249.00,
  "customer": "cus_••••81" }

Noxtill

Payment recordedInvoice INV-5520 marked paid
Fitness studio class reminder in Noxtill

Business scenario

A practical day in the business.

Lakeview Fitness Studio in Madison, MS takes membership payments through an outside payment provider. Admin Joanna Price connected it with a webhook.

  • 6:02 AM — A $249.00 membership payment succeeds. The event arrives, its signature checks out, and invoice INV-5520 is marked paid.
  • 6:02 AM — The provider resends the same event. Same event ID, so it’s ignored.
  • 6:40 AM — A new-customer event is missing an email. It goes to the dead-letter queue with the reason.
  • 9:15 AM — Joanna fixes the mapping and retries it from the queue.

How webhook automation works

A clearer way to work.

  1. 01Create endpointNoxtill gives you a unique URL and a signing secret.
  2. 02Verify signatureEvery delivery is checked against the secret before anything happens.
  3. 03Map payloadChoose which fields create or update which record.
  4. 04Ignore replaysEvents already processed are recognized by ID and skipped.
  5. 05Retry or dead-letterFailures retry, then wait in a queue for review.

Why it matters

Copying events by hand is where records go wrong.

Payments, signups and orders happen in other apps. Without a reliable connection, someone re-types them into your system, or a fragile script creates duplicates when an event is sent twice.

Webhook automation verifies each event, processes it once and keeps a log you can check.

Webhook payload and event log

Interface and key controls

See the details that keep work moving.

Select a delivery to inspect it. Secrets are never shown in full, and failed deliveries can be retried from the dead-letter queue.

Webhook Endpoint: https://hooks.noxtill.example/in/wh_3kd…Secret: whsec_••••••••4f2a (hidden)
Payload inspector
{ "event": "payment.succeeded",
  "id": "evt_5Hq2",
  "amount": 249.00,
  "customer": "cus_••••81" }
Signature: VerifiedResponse: 200 OK
Invoice INV-5520 marked paid.

Business scenarios and exceptions

Designed for real-world exceptions.

Signatures are checked on every delivery, replays are ignored, secrets are never displayed, and anything that can’t be processed waits in a dead-letter queue.

ProcessedSignature verified, event new, record created or updated. The delivery log shows the result.
RetryingProcessing failed for a temporary reason. It retries automatically before going to the queue.
Rejected or dead-letteredBad signature: rejected. Mapping failed after retries: held in the dead-letter queue for review.

FAQs

Webhook automation questions.

Related: Triggers & Actions · Scheduled Workflows

What is a webhook?

A message another app sends when something happens, such as a payment. Noxtill receives it and turns it into a record.

How do you know an event is genuine?

Each delivery is signed with a secret only you and the sending app know. Deliveries with a bad signature are rejected.

What if the same event is sent twice?

Events are tracked by ID. If one has already been processed, the repeat is ignored.

Who should use webhook automation?

Teams and technical admins connecting payment, form, scheduling or other apps to Noxtill.

What happens to events that fail?

They retry automatically, then wait in a dead-letter queue with the error so someone can fix and retry them.

Connect your apps without the copy-paste.

Start a 14-day free trial or book a demo to set up webhook automation.