wundertre.help
Team login

Create, pause and remove webhook subscriptions

Webhook subscriptions send selected WundertreOS events to an external endpoint. Creating a subscription can start ongoing data sharing, so approve the destination and event categories before enabling it.

Prepare the receiving endpoint

Use an endpoint controlled by your organization or an explicitly approved service. Prefer HTTPS. Have your developer prepare the endpoint to receive signed JSON requests and validate their signatures.

The signing secret is sensitive. Store it securely and keep it out of screenshots, recordings and support messages. Review the webhook reference linked from the page for payload details and signature verification.

Review Destination URL and Events to send before creating a subscription.

Review Destination URL and Events to send before creating a subscription.

Create a subscription

  1. Open Settings → Integrations → Webhooks.
  2. Select New Webhook.
  3. Enter Destination URL. Double-check the full address and intended recipient.
  4. Under Events to send, select only the events the receiving service needs. The available groups include Contacts, Deals, Support requests and Social.
  5. Add an optional Description to explain the subscription's purpose.
  6. Review the URL and selected events, then select Create webhook when you are ready to establish the subscription.
  7. If the signing-secret dialog appears, store the secret securely before selecting Done. The dialog says it will not be shown again.
  8. Check the resulting row's Target URL, Events, Description and Status.

The app requires a valid HTTP or HTTPS URL and at least one event. URL validation alone does not prove that the endpoint belongs to the intended recipient or that delivery works.

Available events

  • Contacts: Contact created, Contact updated, Tag added, Contact enriched and Note added.
  • Deals: Deal created and Deal updated.
  • Support requests: Support request submitted, Support request status changed and Support request assigned.
  • Social: Social post failed to publish.

Scroll to review Support requests, Social and the optional Description field.

Scroll to review Support requests, Social and the optional Description field.

Verify delivery

The interface describes signed POST requests and retries with backoff. Its signing guidance uses X-Wunder-Signature with an HMAC-SHA256 signature of the request body.

An Active status describes the subscription setting. To verify end-to-end delivery, use an approved test event and have the receiving service check its request and signature-validation logs. Do not create a real customer event solely for testing unless that action is authorized.

Pause or resume a subscription

Select Pause on the intended active subscription. The status changes to Paused after a successful update. Select Resume when you are ready to enable it again.

Pause and Resume save immediately. Before resuming, recheck that the destination and events are still approved. Do not assume paused events will automatically replay; check the current webhook documentation for delivery behavior.

Remove a subscription

Review the exact destination and dependent workflows, then select Delete when removal is intended. This screen does not show a separate confirmation dialog. Wait for the result and check that the row has been removed.

If you only need a temporary stop, use Pause instead. Deleting a subscription removes its configuration; recreating one requires a new setup and secure handling of its signing secret.

Was this helpful?

Related

Configure social approvals and per-person publishing rules
Social Approvals lets an organization admin decide whose posts need review before they reach social networks. These controls affect teammates’ ability to publish and approve posts.
Understand why a feature is unavailable to your account
A missing or disabled feature can depend on your organization, role, hub access, subscription, usage limits or feature availability. Start with the message on screen rather than changing settings at random.
Set member roles, hub access and prospecting budgets
A teammate's tier defines what they can do, hub access defines where they can work, and a prospecting budget limits their prospecting spend. Review all three before saving.
Invite and manage organization members
Use User Management to invite teammates and review whether they have finished signing in. An invitation, a member record and a completed first sign-in are separate states.