Actions51
- Platforms Actions
- Projects Actions
- Webhooks Actions
- ApiKeys Actions
- Auth Actions
- Identities Actions
- Members Actions
- Messages Actions
- Platform Logs Actions
Overview
This node interacts with the GateKit API to manage webhooks within a specified project. Specifically, the "List" operation under the "Webhooks" resource retrieves all webhooks configured for a given project. This is useful for scenarios where you want to audit, monitor, or programmatically access the list of webhook endpoints that are set up to receive event notifications from the GateKit platform.
Practical examples include:
- Automatically fetching and displaying all webhooks for a project in a dashboard.
- Integrating with other systems to verify webhook configurations.
- Auditing webhook usage or preparing for updates by listing existing webhooks.
Properties
| Name | Meaning |
|---|---|
| Project | Project identifier to operate on (string). Specifies which project's webhooks to list. |
Output
The output will be a JSON array containing webhook objects representing each webhook configured for the specified project. Each webhook object typically includes details such as the webhook's ID, name, target URL, subscribed events, status, and delivery statistics.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating requests to the GateKit API.
- The node uses the base URL and authentication headers configured via the provided API key credential.
- No additional external dependencies are required.
Troubleshooting
Common issues:
- Invalid or missing project identifier: Ensure the "Project" property is correctly set to a valid project ID.
- Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- Network or connectivity problems: Check network access to the GateKit API endpoint.
Common error messages:
- Unauthorized or 401 errors: Indicate invalid or expired API credentials; reconfigure the API key.
- 404 Not Found: The specified project does not exist or is inaccessible.
- Rate limiting or 429 errors: Too many requests; implement retry logic or reduce request frequency.
Links and References
- GateKit API Documentation (general reference for API endpoints)
- n8n documentation on HTTP Request Node for understanding how API calls are made within nodes