Actions52
- ApiKeys Actions
- Auth Actions
- Identities Actions
- Members Actions
- Messages Actions
- Platform Logs Actions
- Platforms Actions
- Projects Actions
- Webhooks Actions
Overview
This node interacts with a universal messaging gateway platform, specifically focusing on managing webhook delivery attempts for event notifications. The "Webhooks" resource with the "Deliveries" operation allows users to list and filter webhook delivery attempts associated with a specific webhook in a project.
Common scenarios where this node is beneficial include:
- Monitoring webhook delivery statuses to ensure event notifications are successfully sent.
- Filtering deliveries by event type or status to troubleshoot failed or pending webhook calls.
- Paginating through large sets of delivery records for auditing or reporting purposes.
Practical example:
- A user wants to retrieve the last 50 successful webhook deliveries for a particular webhook to verify that all message.received events were delivered without issues.
Properties
| Name | Meaning |
|---|---|
| Webhook ID | Identifier of the webhook whose delivery attempts you want to list. |
| Filter by event type | Optional filter to restrict results to a specific event type (e.g., message.received). |
| Filter by delivery status | Optional filter to restrict results by delivery status: pending, success, or failed. |
| Number of deliveries to return (1-100) | Limits the number of delivery records returned; default is 50. |
| Number of deliveries to skip | Number of delivery records to skip for pagination purposes. |
| Project | Identifier of the project containing the webhook. |
Output
The node outputs JSON data representing a list of webhook delivery attempts matching the specified filters. Each delivery record typically includes details such as:
- Delivery status (pending, success, failed)
- Event type
- Timestamp of the delivery attempt
- Possibly additional metadata about the delivery
The output structure enables users to analyze webhook delivery performance and troubleshoot issues.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential configured in n8n to authenticate requests to the messaging gateway API.
- The node makes HTTP GET requests to the endpoint
/api/v1/projects/{project}/webhooks/{webhookId}/deliverieswith query parameters based on input properties. - The user must specify a valid project identifier and webhook ID.
Troubleshooting
- Invalid Webhook ID or Project: If the webhook ID or project does not exist or is incorrect, the API will likely return an error indicating the resource was not found. Verify these identifiers.
- Permission Errors: Insufficient permissions or invalid API credentials may cause authorization errors. Ensure the API key has access to the specified project and webhooks.
- Empty Results: If no deliveries match the filters, the output will be empty. Adjust filters or check if the webhook has recent delivery attempts.
- Pagination Issues: Using offset and limit incorrectly may result in missing or repeated records. Use consistent pagination parameters.
Links and References
- MsgCore API Documentation (replace with actual URL)
- Webhook Management Guide
- Webhook Delivery Status Explanation
Note: URLs are placeholders; please refer to your messaging gateway provider's official documentation.