Task Webhooks
Task webhooks automatically notify external systems when something changes in SCS Tasks — for example, when a task is created or completed. This lets you connect tools like Zapier or your own integrations.
What can I do here?
- Create a new webhook with a target URL and subscribed event types
- Activate or deactivate a webhook
- Send a test delivery to check the connection
- View the delivery log and retry failed deliveries
Step by step
Set up a webhook
- Click Add Webhook, give it a name (e.g. "Zapier Integration") and the target URL.
- Choose the event types this webhook should be informed about.
- Save the webhook. The signing secret is shown only once — copy it immediately so you can verify requests later.
- Click Send Test to send a sample delivery to the configured URL and check the connection.
Check failed deliveries
- Open a webhook and switch to the Delivery Log.
- Filter by status to see, for example, only failed deliveries.
- Use Redeliver to retry a failed delivery.
- 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.
| Name | URL | Subscribed Events | Status |
|---|---|---|---|
| Sample integration | https://example.invalid/hooks/tasks | 3 | ✓Active |
| Sample archive | https://example.invalid/hooks/archive | 1 | •Inactive |
/tasks/webhooks| Event Types | Attempt | Status |
|---|---|---|
| task.created | 1 | ✓Success |
| task.completed | 1 | ✓Success |
| task.updated | 3 | ×Failed |
| task.updated | 1 | !Retrying |
/tasks/webhooksFields explained
| Field | Meaning | Notes/Effect |
|---|---|---|
| Name | Name of the webhook | For identification |
| URL | Target address events are sent to | Must be reachable over HTTPS |
| Signing secret | Secret key used to verify incoming requests on the receiving end | Shown in plain text only once |
| Event types | The events this webhook is informed about | See value list below |
| Max retries | How many times a failed delivery is automatically retried | — |
| Timeout (ms) | How long to wait for a response from the target server | After this, the delivery counts as failed |
| Active | Whether the webhook sends events at all | Inactive webhooks send nothing |
| Attempt | Sequence number of a delivery attempt in the log | — |
Values & Status
Event types
| Label | Meaning |
|---|---|
| task.created | A new task was created |
| task.updated | A task was changed |
| task.completed | A task was completed |
| task.deleted | A task was deleted |
| comment.created | A new comment was added |
| project.created | A new project was created |
| project.updated | A project was changed |
| project.deleted | A project was deleted |
| membership.changed | Project membership changed |
| webhook.test | Test event, triggered via "Send Test" |
Delivery status
| Label | Plain meaning | What happens then |
|---|---|---|
| Success | The delivery was confirmed by the target server | No further action needed |
| Failed | The delivery could not be completed successfully | Can be retried manually via "Redeliver" |
| Retrying | The delivery is being automatically retried | Up to the configured "Max retries" |
| Pending | The delivery hasn't been processed yet | — |
Frequently asked questions
How do I verify that an incoming request actually came from SELLERLOGIC Commerce Services?
Every delivery is signed with the signing secret. Your receiving system should verify this signature before processing the payload.
What happens if I didn't copy the signing secret right away?
For security reasons it's shown in plain text only once. You'll need to recreate the webhook or reset the secret to get a new one.
How many times is a failed delivery retried automatically?
Up to the configured "Max retries" count — after that it stays "Failed" and can be redelivered manually.