Boomerangme icon

Boomerangme

Interact with Boomerangme API

Overview

The node interacts with the Boomerangme API, specifically allowing operations on various resources such as Customer, Card, Company, and SMS. For the Customer resource with the List operation, it fetches a list of customers from the Boomerangme service. This is useful for scenarios where you want to retrieve customer data filtered by specific criteria like phone number or email address.

Practical examples include:

  • Retrieving all customers who have a particular phone number.
  • Fetching customers filtered by their email addresses for marketing or support purposes.

Properties

Name Meaning
Phone Filter the list of customers by phone number (string input).
Email Filter the list of customers by email address (string input).

These properties allow you to narrow down the list of customers returned by the API based on phone or email filters.

Output

The node outputs JSON data representing the list of customers retrieved from the Boomerangme API. Each item in the output corresponds to a customer object containing details as provided by the API.

If binary data were involved, it would be summarized here, but this operation deals only with JSON customer data.

Dependencies

  • Requires an API key credential for authenticating with the Boomerangme API.
  • The base URL used for requests is https://api.digitalwallet.cards/api/v2.
  • Proper configuration of the API authentication credential within n8n is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Providing invalid filter values (e.g., malformed email) may result in no data or errors.
    • Network connectivity issues can prevent successful API calls.
  • Error messages:

    • Authentication errors typically indicate problems with the API key; verify that the correct key is configured.
    • Validation errors may occur if filter parameters do not meet expected formats; ensure phone and email inputs are valid.
    • Timeout or connection errors suggest network problems; check your internet connection and API availability.

Links and References

Discussion