Webhook deliveries
One event to send to one webhook: its state, attempts and last result. Each attempt also writes a webhook log.
- API name:
webhookdeliveries - Domain: Features
- Modules: Administration
Fields
The API name is what the API, MCP and the CLI use.
| Name | API name | Type | Required | Description |
|---|---|---|---|---|
| ID | id | Record ID | Yes | |
| Webhook | webhookId | Reference | Yes | |
| Event | eventId | Reference | Yes | |
| Cycle | cycle | Whole Number | Yes | 0 for the delivery the drain wrote. Each redeliver adds a new delivery with the next number; the earlier ones keep their result. |
| Attempts | countAttempt | Whole Number | Yes | Requests sent for this delivery. At 5 failed attempts the delivery is dead. |
| Error | errorMessage | Text Area | ||
| Status | status | Constant | Yes | Pending waits for its next attempt, delivering is being sent, delivered got a 2xx answer, dead used every attempt. |
| HTTP status | httpStatus | Integer | Status code of the last answer. Empty when the request did not reach the webhook. | |
| Last attempt | lastAttemptAt | Date and Time | ||
| Created at | createdAt | Date and Time | Yes |
Relations
Actions
What you can do with a record. Every action also sends the webhook event webhookdeliveries.<action>. Reads (find, get, count) work on every table.
| Name | API name | Description | Where |
|---|---|---|---|
| Redeliver | redeliver | Queue the event again for its webhook as a new delivery. This delivery keeps its result. | App · API · CLI |