Boomerangme icon

Boomerangme

Interact with Boomerangme API

Actions23

Overview

This node integrates with the Boomerangme API to interact with digital wallet cards and related entities. Specifically, for the Card resource and the List of Cards operation, it retrieves a list of cards filtered by various optional criteria such as template ID, customer ID, customer phone, or customer email.

Common scenarios where this node is useful include:

  • Fetching all cards associated with a particular customer or template.
  • Filtering cards based on customer contact details to manage or audit card distributions.
  • Integrating card data retrieval into workflows that automate customer engagement or marketing campaigns.

Example use case: A marketing automation workflow could use this node to list all cards linked to customers with a specific email domain, then send targeted SMS promotions.

Properties

Name Meaning
Template ID Filter the list of cards by a specific template identifier.
Customer ID Filter the list of cards by a specific customer identifier.
Customer Phone Filter the list of cards by the customer's phone number.
Customer Email Filter the list of cards by the customer's email address.

Output

The node outputs JSON data representing the list of cards retrieved from the Boomerangme API. Each item in the output array corresponds to a card object containing its details as returned by the API.

If the API supports binary data (e.g., card images or attachments), the node would handle it accordingly, but based on the provided code and properties, the primary output is structured JSON data about cards.

Dependencies

  • Requires an active connection to the Boomerangme API via an API key credential configured in n8n.
  • The base URL for API requests is https://api.digitalwallet.cards/api/v2.
  • Proper API authentication credentials must be set up in n8n before using this node.

Troubleshooting

  • Empty results: If no cards are returned, verify that the filter parameters (Template ID, Customer ID, Phone, Email) are correct and correspond to existing records.
  • Authentication errors: Ensure the API key credential is valid and has sufficient permissions.
  • API connectivity issues: Check network access to api.digitalwallet.cards and confirm the API service is operational.
  • Invalid parameter format: Make sure filter values are correctly formatted strings; incorrect types may cause request failures.

Links and References

Discussion