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 adds a field named transaction_search to the output JSON. This field contains the result of the transaction search operation, which includes the details retrieved for the specified transaction ID.
Example output structure:
{
"transaction_search": { /* transaction details object */ }
}
- The rest of the input data is preserved and passed through unchanged.
Dependencies
- External Service: Requires access to a partner service via the
PartnerServiceFactory. - Credentials: Needs valid
numiKeyApicredentials configured in n8n.
Troubleshooting
- Missing or Invalid Credentials: If the
numiKeyApicredential 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.
- Network Issues: Connectivity problems between n8n and the partner service can cause failures. Check your network connection and any firewall settings.