Numi Transaction Search icon

Numi Transaction Search

Numi Transaction Search Node

Overview

The Numi Transaction Search node allows users to search for transaction details using a specific transaction ID. This node is useful in workflows where you need to retrieve information about a particular transaction, such as verifying payment status, fetching transaction metadata, or integrating with other systems that require transaction details.

Practical examples:

  • Automatically checking the status of a payment after a customer completes a purchase.
  • Fetching transaction details to include in an email notification or report.
  • Validating transaction IDs before processing refunds or follow-up actions.

Properties

Name Meaning
ID Transaction The unique identifier of the transaction you want to look up. This is required and should be provided as a string (e.g., "123456789").

Output

The node outputs a JSON object with the following structure:

{
  "transaction_search": { /* transaction details object returned from the service */ }
}
  • transaction_search: Contains the details of the transaction retrieved using the provided ID. The exact structure depends on the response from the underlying partner service but typically includes fields relevant to the transaction.

Dependencies

  • External Service: Requires access to a partner service via the PartnerServiceFactory (from the imported partnerServices module).
  • API Key: You must configure valid credentials named numiKeyApi in n8n for this node to function.

Troubleshooting

  • Missing or Invalid API Key: If the numiKeyApi credential is not set up or is invalid, the node will fail to connect to the external service. Ensure your credentials are correctly configured in n8n.
  • Invalid Transaction ID: Providing an incorrect or non-existent transaction ID may result in empty results or an error from the partner service. Double-check the ID value.
  • Service Unavailable: If the partner service is down or unreachable, the node will throw an error. Check network connectivity and service status.

Links and References

Discussion