Pular para o conteúdo principal

Complete webhook create and test flow

This guide walks through creating and testing a webhook end to end. Read webhooks and webhook security first.

For delivery failures after launch, see webhook delivery failures.


Part 1 — Plan and create

  1. Confirm you are in the correct business workspace.

[Screenshot: App header — correct business workspace selected.]

  1. Document which events your automation needs (approved sale, subscription, etc.).

[Screenshot: Event plan — required webhook events listed.]

  1. Open IntegrationsWebhooks → create webhook.

[Screenshot: Create webhook — new webhook form opened.]

  1. Enter HTTPS endpoint URL (publicly reachable).

[Screenshot: Endpoint URL — valid HTTPS URL entered.]

  1. Select events — prefer approved sale events over PIX generated alone.

[Screenshot: Event checkboxes — approved purchase events selected.]

  1. Save webhook and note signing secret if shown. See webhook security.

[Screenshot: Webhook secret — signing key copied securely.]


Part 2 — Simulator test

  1. Open webhook simulator for one selected event type.

[Screenshot: Simulator — test event type chosen.]

  1. Send simulated payload to endpoint.

[Screenshot: Simulator send — test delivery triggered.]

  1. Open delivery logs — confirm 2xx success response.

[Screenshot: Logs — simulator delivery success with 200 status.]

  1. Verify external system (Zapier, Make, custom API) received payload.

[Screenshot: External system — test event received and parsed.]

  1. If failed, fix endpoint before production. See Zapier/Make.

[Screenshot: Endpoint fix — error response resolved to 200.]


Part 3 — Production verification

  1. Run safe test purchase on staging or low-value offer.

[Screenshot: Test checkout — purchase completed for webhook test.]

  1. Confirm sale approved in Sales.

[Screenshot: Sales — approved test sale for webhook trigger.]

  1. Check webhook logs for production delivery attempt.

[Screenshot: Production log — real event delivered successfully.]

  1. Confirm external automation runs once (no duplicate processing).

[Screenshot: External automation — single execution for one sale.]

  1. Enable monitoring alert for failed deliveries if available.

[Screenshot: Monitoring — alert or log review scheduled.]


Event selection cheat sheet

EventSafe for delivery?
Sale approvedYes
PIX generated onlyNo — not paid
Cart abandonedRecovery only
Subscription canceledAccess workflows