Guru Digital Manager icon

Guru Digital Manager

Interact with Guru Digital Manager API

Actions39

Overview

The node "Guru Digital Manager" integrates with the Guru Digital Manager API to manage various resources such as contacts, transactions, subscriptions, and webhooks. Specifically, for the Webhook - Create operation, this node allows users to create new webhooks by specifying a target URL, events to listen for, and the webhook's status.

This is useful in scenarios where you want to automate workflows triggered by specific events in the Guru Digital Manager system, such as when a contact or transaction is created or updated. For example, you can create a webhook that listens for "Contact Created" events and triggers downstream automation whenever a new contact is added.

Properties

Name Meaning
URL The destination URL where webhook notifications will be sent.
Events The list of events to listen for. Options include: Contact Created, Contact Updated, Transaction Created, Transaction Updated, Subscription Created, Subscription Updated.
Status The status of the webhook. Can be either "Active" or "Inactive".

Output

  • The output is a JSON array containing the response from the Guru Digital Manager API after creating the webhook.
  • The JSON structure corresponds to the newly created webhook object returned by the API, typically including details like the webhook ID, URL, subscribed events, status, and timestamps.
  • No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential (referred generically as an API authentication token) for the Guru Digital Manager API.
  • The base URL for the API defaults to https://digitalmanager.guru/api/v2 but can be overridden via credentials.
  • The node uses HTTP requests with Bearer token authorization to communicate with the API.

Troubleshooting

  • Missing Credentials Error: If the API key credential is not provided or invalid, the node throws an error indicating credentials are required.
  • HTTP Request Failures: Network issues or incorrect URLs may cause request failures. Ensure the base URL and webhook URL are correct.
  • Invalid Event Selection: Selecting no events or unsupported events may cause the API to reject the webhook creation.
  • API Permission Issues: If the API token lacks permissions to create webhooks, the API will return an error.
  • Error Messages: Errors from the API are propagated; check the message for details such as invalid parameters or authentication failure.

To resolve these:

  • Verify the API token and its permissions.
  • Confirm the webhook URL is reachable and correctly formatted.
  • Ensure at least one valid event is selected.
  • Check network connectivity and API endpoint correctness.

Links and References

Discussion