Webhooks (CRM)
Webhooks automatically notify external systems as soon as something specific happens in the CRM — for example, that a ticket was created or a deal moved to a new stage. The connected system then automatically receives a message at a target URL you provide, without anyone needing to manually export anything.
What can I do here?
- Create, edit, and delete webhooks
- Define which event types trigger a webhook
- Set a target URL and a signing secret the receiving system can use to verify the message's authenticity
- Configure maximum retries and a delivery timeout
- Trigger a test send to check the connection
- View the delivery log per webhook and redeliver failed deliveries
Step by step
- Click "Add Webhook", give it a name (e.g. "Zapier Integration"), and enter the target URL.
- Choose the event types that should trigger this webhook.
- Optionally set a signing secret, maximum retries, and a timeout, then save.
- Use "Send Test" to check whether the target URL is reachable and responds correctly.
- Check the delivery log to confirm real events were delivered successfully, and use "Redeliver" for a failed delivery if needed.
- "Redeliver" asks before it sends, naming the target address the signed delivery goes to. Read the address, then confirm.
Why does it ask? A redelivery is not a local retry. The payload goes to the foreign system with a valid signature - there it is indistinguishable from the original delivery, and nothing on this screen can recall it.
Fields explained
| Field | Meaning | Notes/Effect |
|---|---|---|
| Name | The webhook's name | |
| URL | Target address the notification is sent to | |
| Signing Secret | Shared secret used to verify message authenticity on the receiving end | |
| Event Types | Selection of events that trigger this webhook | See "Values & statuses" below |
| Max Retries | How many times a failed delivery is retried | |
| Timeout (ms) | How long to wait for a response from the target system | |
| Active | Whether the webhook currently fires | |
| Delivery Log | List of all delivery attempts with status and attempt number | See "Values & statuses" below |
Values & statuses
Event types (crm_webhook_event)
Ticket Created, Ticket Updated, Ticket Resolved, Deal Stage Changed, Sync Completed, Contact Created, Task Created, Task Updated, Task Completed.
Delivery status (crm_webhook_delivery_status)
| Value | Plain-language meaning |
|---|---|
| Success | The target application acknowledged the message |
| Failed | The delivery ultimately failed |
| Retrying | The delivery is currently being retried |
| Pending | The delivery hasn't run yet |
Frequently asked questions
What's the signing secret for?
It lets the receiving system verify that a message really came from SELLERLOGIC Commerce Services and wasn't forged.
What happens if the target URL is unreachable?
Delivery is retried up to the configured number of retries; after that it's marked failed and shows up accordingly in the delivery log.
Can I manually retrigger a failed delivery?
Yes, using "Redeliver" in the delivery log.