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" integrates with the Guru Digital Manager API, allowing users to manage various resources such as contacts, transactions, subscriptions, and webhooks. Specifically, for the Webhook - Update operation, this node updates an existing webhook's configuration by its ID.
This operation is useful when you want to modify the URL, events listened to, or status of a webhook without recreating it. For example, you might update a webhook to listen to new event types or change its active/inactive status based on your workflow needs.
Practical examples:
- Change the webhook URL to a new endpoint after migrating your server.
- Add or remove event types that the webhook listens for (e.g., start listening for "subscription.updated").
- Deactivate a webhook temporarily by setting its status to inactive.
Properties
| Name | Meaning |
|---|---|
| Webhook ID | The unique identifier of the webhook to update. |
| Webhook Data | A collection of fields to update on the webhook: |
| URL | The new URL where the webhook will send event notifications. |
| Events | List of event types the webhook should listen for. Options include: |
| - Contact Created | |
| - Contact Updated | |
| - Transaction Created | |
| - Transaction Updated | |
| - Subscription Created | |
| - Subscription Updated | |
| Status | The webhook's status, either "Active" or "Inactive". |
Output
The output JSON contains the updated webhook object returned from the Guru Digital Manager API after a successful update. This typically includes the webhook's ID, URL, subscribed events, status, and other metadata as provided by the API.
If the update operation fails, the node throws an error unless configured to continue on failure, in which case the error message is included in the output.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Guru Digital Manager API.
- The base URL for the API is configurable via credentials but defaults to
https://digitalmanager.guru/api/v2. - The node uses HTTP requests with Bearer token authorization to interact with the API.
Troubleshooting
- Missing Credentials Error: If no API credentials are provided, the node will throw an error indicating credentials are required.
- Invalid Webhook ID: Providing an incorrect or non-existent webhook ID will result in an API error. Verify the webhook ID exists before updating.
- Permission Issues: Ensure the API token has sufficient permissions to update webhooks.
- Network or API Errors: Check network connectivity and API availability if requests fail.
- Malformed Input: Make sure the webhook data fields (URL, events, status) are correctly formatted and valid according to API specifications.
Links and References
- Guru Digital Manager API Documentation (general): https://docs.digitalmanager.guru/developers/
- Webhooks API Reference (assumed location): https://docs.digitalmanager.guru/developers/webhooks