Guru Digital Manager icon

Guru Digital Manager

Interact with Guru Digital Manager API
Join our community

Actions39

Overview

This node integrates with the Guru Digital Manager API, allowing users to manage various resources such as contacts, transactions, subscriptions, affiliations, checkouts, countries, coupons, products, users, and webhooks. Specifically for the Webhook - Get operation, it retrieves detailed information about a specific webhook by its ID.

Typical use cases include:

  • Fetching configuration details of a webhook to verify its URL, subscribed events, or status.
  • Auditing or troubleshooting webhook setups in automated workflows.
  • Integrating webhook data retrieval into larger automation processes where webhook metadata is needed.

Example: You want to get the details of a webhook you previously created to confirm which events it listens to and whether it is active.

Properties

Name Meaning
Webhook ID The unique identifier of the webhook you want to retrieve. This is required for the Get operation on the Webhook resource.

Output

The output is a JSON object representing the webhook's details as returned by the Guru Digital Manager API. It typically includes fields such as:

  • id: The webhook's unique identifier.
  • url: The URL endpoint configured for the webhook.
  • events: An array of event types the webhook listens to (e.g., contact.created, transaction.updated).
  • status: The current status of the webhook (e.g., active, inactive).
  • Other metadata related to the webhook configuration.

If multiple webhooks are retrieved (in other operations), the output would be an array of such objects.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authentication 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 communicate with the API.

Troubleshooting

  • Missing Credentials Error: If no API credentials are provided, the node throws an error indicating credentials are required.
  • Invalid Webhook ID: If the webhook ID does not exist or is incorrect, the API will likely return a 404 error. Verify the ID and ensure it exists.
  • Permission Issues: If the API token lacks permission to access webhook data, the request will fail. Ensure the token has appropriate scopes.
  • API Endpoint Issues: The node uses a default base URL but allows override via credentials. Confirm the base URL is correct if requests fail.
  • Network or Connectivity Problems: Standard HTTP errors may occur due to network issues; check connectivity and firewall settings.

Links and References

Discussion