Guru Digital Manager icon

Guru Digital Manager

Interact with Guru Digital Manager API
Join our community

Actions39

Overview

The "Guru Digital Manager" node integrates with the Guru Digital Manager API, enabling users to manage various resources such as contacts, transactions, subscriptions, and more. Specifically, for the Transaction - Get operation, this node retrieves detailed information about a single transaction by its unique ID.

This operation is useful when you need to fetch the current state or details of a specific transaction, for example:

  • Verifying payment status before fulfilling an order.
  • Retrieving transaction metadata for reporting or auditing.
  • Integrating transaction data into other workflows or systems.

The node handles multiple fallback URLs to ensure robust retrieval of transaction data even if some endpoints return 404 errors.

Properties

Name Meaning
Transaction ID The unique identifier of the transaction to retrieve (e.g., tr_043tzaioaeBMAxAnG). You can obtain valid IDs using the "Get All" operation first.

Output

The output is a JSON object representing the transaction details as returned by the Guru Digital Manager API. This typically includes fields such as transaction amount, status, description, timestamps, and related metadata.

If the transaction is successfully retrieved, the output will contain all available transaction data in JSON format.

No binary data output is produced by 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; 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 that credentials are required. Ensure you have configured a valid API authentication token in the node's credentials.

  • Transaction Not Found (404): If the transaction ID does not exist or is incorrect, the node attempts several alternative API endpoints to locate the transaction. If all fail, it throws an error suggesting to verify:

    1. The correctness and existence of the transaction ID.
    2. That the API token has permission to access transactions.
    3. The base URL configured in credentials is correct.
    4. Consult the official API documentation for further guidance.

  • API Permission Issues: Errors related to authorization may occur if the API token lacks necessary permissions. Verify your API key scopes and permissions.

  • Network or Endpoint Issues: If the API base URL is unreachable or incorrect, requests will fail. Confirm network connectivity and correct API endpoint configuration.

Links and References

Discussion