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 to manage various resources such as contacts, transactions, subscriptions, and more. Specifically, for the Transaction - Get All operation, this node fetches a list of transactions from the API, supporting multiple filtering options and pagination.

This operation is useful when you want to retrieve multiple transaction records based on specific criteria like date ranges, status, contact details, or product IDs. For example, you could use it to:

  • Retrieve all completed transactions within a certain date range.
  • Filter transactions by payment type or marketplace.
  • Paginate through large sets of transactions using cursors.

Practical scenarios include financial reporting, auditing transactions, syncing transaction data with other systems, or monitoring transaction statuses in bulk.

Properties

Name Meaning
Cancelled At Start Filter transactions canceled on or after this date (format: YYYY-MM-DD).
Cancelled At End Filter transactions canceled on or before this date (format: YYYY-MM-DD).
Confirmed At Start Filter transactions confirmed on or after this date (format: YYYY-MM-DD).
Confirmed At End Filter transactions confirmed on or before this date (format: YYYY-MM-DD).
Contact ID Filter transactions associated with a specific contact ID.
Contact Document Filter transactions by the contact's document identifier.
Contact Email Filter transactions by the contact's email address.
Contact Name Filter transactions by the contact's name.
Cursor Pagination cursor to fetch the next page of results.
Invoice ID Filter transactions linked to a specific invoice ID.
Marketplace ID Filter transactions by a specific marketplace ID.
Marketplaces Filter transactions by one or more marketplaces (comma-separated list).
Ordered At Start Filter transactions ordered on or after this date (format: YYYY-MM-DD).
Ordered At End Filter transactions ordered on or before this date (format: YYYY-MM-DD).
Payment Types Filter transactions by payment types (comma-separated list).
Product ID Filter transactions related to a specific product ID.
Subscription ID Filter transactions related to a specific subscription ID.
Transaction Status Filter transactions by one or more statuses. Options include: Abandoned, Analysis, Approved, Billet Printed, Blocked, Canceled, Chargeback, Completed, Delayed, Dispute, Expired, In Recovery, Refunded, Rejected, Scheduled, Started, Trial, Waiting Payment.

Output

The output is a JSON array containing transaction objects returned by the Guru Digital Manager API. Each object represents a transaction record with fields as defined by the API, typically including identifiers, amounts, statuses, dates, and related entity references.

If multiple transactions are returned, they are included as separate items in the output array.

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 defaults to https://digitalmanager.guru/api/v2 but can be customized via credentials.
  • The node uses HTTP requests with Bearer token authentication.
  • Proper permissions on the API token are necessary to access transaction data.

Troubleshooting

  • Missing Credentials Error: If no API credentials are provided, the node will throw an error indicating credentials are required.
  • 404 Not Found Errors: When fetching a transaction by ID, if the transaction does not exist or the ID is incorrect, the API returns 404. The node attempts multiple alternative endpoints to locate the transaction. If all fail, it throws a detailed error suggesting to verify the transaction ID, API token permissions, base URL, and consult the API documentation.
  • Rate Limits or API Errors: Standard HTTP errors from the API may occur; ensure your API token has sufficient permissions and that the API service is operational.
  • Pagination Issues: Use the Cursor property correctly to paginate through results. Omitting or misusing it may result in incomplete data retrieval.
  • Filter Format: Date filters must be in YYYY-MM-DD format. Incorrect formats may cause the API to reject the request.

Links and References

Discussion