Overview
The Numi Transactions node retrieves transaction data associated with a user’s phone number from the Numi service. It allows filtering transactions by type (such as send or request) and status (such as complete, pending, etc.). This node is useful for automating workflows that require access to a user's transaction history, such as reporting, monitoring, or triggering actions based on transaction events.
Practical examples:
- Fetching all recent transactions for a given user.
- Filtering only "send" or "request" transactions for auditing purposes.
- Monitoring transactions with specific statuses (e.g., only completed or pending).
Properties
| Name | Meaning |
|---|---|
| Operation | Selects the operation to perform. Options: Get Transactions (retrieves Numi transactions). |
| Types | Filters transactions by type. Options: All (all transactions), Send (send transactions), Request (request transactions). |
| Status | Filters transactions by status. Options: All (all transactions), Complete (complete transactions), Expired (expired transactions), In_progress (in-progress transactions), Pending (pending transactions), WaitingSenderToBeChargedByCashload (waiting for sender to be charged by Cashload). |
| User Phone Number | The user's telephone number to obtain their transactions. This field is required. |
Output
json.transactions: An array of transaction objects matching the selected filters. Each object contains detailed information about a transaction.json.transactions_list_Reply: An array of up to 10 summary objects for the filtered transactions. Each summary object includes:id: The platform ID of the transaction.title: Status details (e.g., sender's name).description: Reason or description of the transaction (for requests, this includes amount, currency, and a human-readable date).
Dependencies
- External Service: Requires access to the Numi API via the
PartnerServiceFactory. - Credentials: Needs a configured credential named
numiKeyApiin n8n.
Troubleshooting
Common issues:
- Missing or invalid credentials: If the
numiKeyApicredential is not set up correctly, the node will fail to connect to the Numi service. - Invalid or missing phone number: The "User Phone Number" property is required; omitting it will result in an error.
- No transactions found: If there are no transactions matching the filters, the output arrays may be empty.
Error messages and resolutions:
- "Cannot read property 'getOperations' of undefined" – Ensure the Numi credentials are valid and the service is reachable.
- "User Phone Number is required" – Make sure to provide a valid phone number in the input.
Links and References
- n8n Documentation
- Numi API documentation (contact your Numi partner representative for access)