Actions51
- Platforms Actions
- Projects Actions
- Webhooks Actions
- ApiKeys Actions
- Auth Actions
- Identities Actions
- Members Actions
- Messages Actions
- Platform Logs Actions
Overview
This node integrates with the GateKit universal messaging gateway API, enabling users to manage webhooks for event notifications within a specified project. Specifically, the "Get" operation under the "Webhooks" resource retrieves detailed information about a specific webhook, including its delivery statistics.
Use cases include:
- Monitoring webhook configurations and their status.
- Retrieving delivery metrics to troubleshoot or analyze webhook performance.
- Managing event-driven integrations by inspecting webhook details.
For example, a user can fetch the configuration and recent delivery stats of a webhook that listens for message events in a messaging platform integrated via GateKit.
Properties
| Name | Meaning |
|---|---|
| Webhook ID | The unique identifier of the webhook to retrieve. |
| Project | The project identifier within which the webhook exists; used to scope the request. |
Note: The property list includes multiple entries named "WebhookId" or "webhookId" due to source duplication, but effectively they represent the same required string input identifying the webhook.
Output
The node outputs JSON data representing the webhook's details and its delivery statistics. This typically includes:
- Webhook configuration (e.g., name, URL, subscribed events).
- Status indicators such as whether the webhook is active.
- Delivery attempt records showing success/failure counts and timestamps.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating requests to the GateKit API.
- The node uses the base URL from the provided credentials to construct API calls.
- Proper project identification is necessary to scope webhook operations.
Troubleshooting
- Invalid Webhook ID: If the webhook ID does not exist or is malformed, the API will likely return a 404 error. Verify the webhook ID is correct.
- Authentication Errors: Missing or invalid API key credentials will cause authentication failures. Ensure valid credentials are configured.
- Project Not Found: Using an incorrect project identifier may result in errors. Confirm the project parameter matches an existing project.
- Network Issues: Connectivity problems to the GateKit API endpoint can cause timeouts or connection errors.
To resolve these issues, verify all input parameters, ensure credentials are correctly set up, and check network connectivity.
Links and References
- GateKit API Documentation (hypothetical link; replace with actual if available)
- n8n documentation on HTTP Request Node for understanding API call mechanics