Actions39
- Contact Actions
- Transaction Actions
- Subscription Actions
- Affiliation Actions
- Checkout Actions
- Country Actions
- Coupon Actions
- Product Actions
- User Actions
- Webhook Actions
Overview
The node "Guru Digital Manager" allows interaction with the Guru Digital Manager API to manage various resources such as contacts, transactions, subscriptions, affiliations, checkouts, countries, coupons, products, users, and webhooks. Specifically, for the Webhook resource with the Get All operation, this node fetches a list of all webhooks configured in the Guru Digital Manager system.
This operation is useful when you want to retrieve all webhook configurations to monitor or audit them, or to use their details in further automation workflows. For example, you might want to get all active webhooks to verify which events your system is currently listening to or to synchronize webhook data with another system.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all webhook results or only up to a given limit (boolean). |
| Limit | Maximum number of webhook results to return if "Return All" is false (number, 1-100). |
These properties control pagination of the results when fetching multiple webhooks.
Output
The output is a JSON array where each element represents a webhook object retrieved from the Guru Digital Manager API. Each webhook object typically contains fields such as:
id: The unique identifier of the webhook.url: The URL to which the webhook sends event notifications.events: An array of event types that the webhook listens for (e.g., contact.created, transaction.updated).status: The status of the webhook (e.g., active, inactive).
If multiple webhooks are returned, they are included as separate objects within the output array.
The node does not output binary data.
Dependencies
- Requires an API key credential for authentication with the Guru Digital Manager API.
- The base URL for the API defaults to
https://digitalmanager.guru/api/v2but can be overridden in credentials. - The node uses HTTP requests with Bearer token authorization to communicate with the API.
Troubleshooting
- Missing Credentials Error: If no API credentials are provided, the node throws an error indicating credentials are required. Ensure you have configured the necessary API authentication token.
- API Request Failures: Network issues or incorrect base URL settings may cause request failures. Verify the base URL and network connectivity.
- Limit and Pagination: If you do not set "Return All" to true and specify a limit, only that many webhooks will be returned. To get all webhooks, enable "Return All".
- Unexpected API Responses: If the API changes or returns unexpected data, the node may fail. Check the Guru Digital Manager API documentation for updates.
Links and References
- Guru Digital Manager API Documentation (for detailed API endpoints and webhook schema)
- n8n Documentation on HTTP Request Node (for understanding how HTTP requests work in n8n)
This summary focuses exclusively on the Webhook resource's Get All operation as requested.