Knowledge Base

HR Webhooks

A webhook automatically notifies an external system whenever a specific HR event happens in SELLERLOGIC Commerce Services — for example, that a new employee was created or a time-off request was approved. You provide the external system's web address and choose which events should trigger a notification. SCS then automatically sends a message there as soon as the event occurs. This page is aimed mainly at technically minded people or the IT department who are setting up a connection to an external system.

Rebuilt excerpt of the view: /hr/webhooks

What can I do here?

  • Search all configured webhooks
  • Create a new webhook with a target address and event types
  • Edit, activate/deactivate, or delete a webhook
  • Trigger a test send to a webhook
  • View a webhook's delivery log and resend failed deliveries

Step by step

Create a new webhook

  1. Click "Add Webhook" in the top right corner.
  2. Enter a name, the URL of the external system, and optionally max retries and timeout (ms).
  3. Under "Event Types", select at least one event that should trigger the webhook.
  4. Click "Create".

Test a webhook

  1. Open the webhook by clicking its entry in the list.
  2. Click "Send Test" in the side panel. A test event is sent to the configured URL immediately.

Resend a failed delivery

  1. Open the webhook and scroll to the delivery log.
  2. Click "Redeliver" on an entry with status "Failed" or "Retrying".
  3. A confirmation appears 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 Name of the webhook Required, for your own overview only
URL Web address of the external system the notification is sent to Must be a valid, publicly reachable HTTPS address; internal/local addresses are rejected for security reasons
Signing Secret Secret value used to secure the delivery Generated automatically, hidden by default, can be revealed with the eye icon
Event Types The HR events that trigger the webhook At least one event required
Max Retries How many times a failed delivery is automatically retried —
Timeout (ms) How long to wait for a response from the external system before the attempt counts as failed In milliseconds
Active Whether the webhook currently fires A deactivated webhook sends no notifications
Delivery Log History of all delivery attempts for this webhook Shows status, event type, HTTP status (if any), and error message per attempt

Values & statuses

Delivery status

Value Meaning What happens
Pending The delivery hasn't been attempted yet Waiting for the next send attempt
Success The external system accepted the notification No further action needed
Failed The delivery has permanently failed (all retries exhausted) Can be retried manually with "Redeliver"
Retrying The delivery failed but is being automatically retried Will be automatically re-delivered shortly

Frequently asked questions

Who is this page for?
For people setting up a technical connection to an external system — typically the IT department or a technical service provider, since a valid target address for the external system is required.

Why does SCS reject some URLs?
For security reasons, only publicly reachable addresses are accepted — local, internal, or private network addresses (e.g. "localhost" or addresses from internal network ranges) are not allowed.

What is the signing secret for?
A secret value the receiving system can use to verify that an incoming message genuinely came from SCS and wasn't forged by a third party.

What happens if I delete a webhook?
The webhook and its entire delivery log are removed; no further notifications are sent afterward.