Guru Digital Manager icon

Guru Digital Manager

Interact with Guru Digital Manager API

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 Contact resource with the Get All operation, this node fetches a list of contacts from the API, optionally filtered by several criteria.

This operation is useful when you want to retrieve multiple contact records in bulk, for example:

  • Synchronizing contacts from Guru Digital Manager into another system.
  • Generating reports or analytics based on contact data.
  • Filtering contacts created within a specific date range or matching certain attributes like email or document number.

Properties

Name Meaning
Additional Fields Optional filters to narrow down the contacts returned. Possible fields:
- Created At Start (date): Filter contacts created after this date (YYYY-MM-DD).
- Created At End (date): Filter contacts created before this date (YYYY-MM-DD).
- Cursor (string): Pagination cursor to fetch the next page of results.
- Document (string): Filter by contact document number (CPF/CNPJ).
- Email (string): Filter by contact email address.
- Name (string): Filter by contact name.
Return All Boolean flag indicating whether to return all matching contacts or limit the number.
Limit Maximum number of contacts to return if Return All is false. Range: 1 to 100.

Output

The output is a JSON array where each element represents a contact object retrieved from the Guru Digital Manager API. Each contact object contains the contact's details as provided by the API, such as name, email, phone, document, creation date, and other relevant fields.

No binary data is output by this operation.

Dependencies

  • Requires an API key credential for Guru Digital Manager with appropriate permissions.
  • The node uses the base URL from credentials or defaults to https://digitalmanager.guru/api/v2.
  • Network access to the Guru Digital Manager API endpoint is required.

Troubleshooting

  • Missing Credentials Error: If the API key credential is not set or invalid, the node will throw an error stating that credentials are required.
  • API Request Failures: Network issues or incorrect base URL can cause request failures. Verify the base URL in credentials and network connectivity.
  • Pagination Issues: When using cursors for pagination, ensure the cursor value is valid; otherwise, no results or errors may occur.
  • Filter Misconfiguration: Providing invalid filter values (e.g., wrong date format) may result in empty responses or API errors.
  • Limit Exceeded: The API limits the maximum number of results per request to 100. Setting a higher limit will be capped or rejected.

Links and References

Discussion