Numi transactions icon

Numi transactions

Numi Transactions Node
Join our community

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 (e.g., send, request) and status (e.g., complete, pending). This node is useful for automating workflows that require access to a user's transaction history, such as reporting, monitoring payment statuses, or triggering actions based on transaction events.

Practical examples:

  • Fetching all transactions for a specific user to generate a financial report.
  • Filtering only "send" transactions that are "pending" for follow-up notifications.
  • Retrieving "request" transactions to analyze outstanding payment requests.

Properties

Name Meaning
Operation Selects the operation to perform. Options:
• Get Transactions – Retrieve Numi transactions.
Types Filters transactions by type. Options:
• All – Get all transactions
• Send – Get send transactions
• Request – Get request transactions
Status Filters transactions by status. Options:
• All – Get all transactions
• Complete – Get complete transactions
• Expired – Get expired transactions
• In_progress – Get in-progress transactions
• Pending – Get pending transactions
• WaitingSenderToBeChargedByCashload – Get transactions waiting for sender to be charged by Cashload
User Phone Number User telephone number to obtain contacts. Required field.

Output

  • The output contains two main fields in the json property:
    • transactions: An array of full transaction objects matching the filters. Each object includes details such as type, status, amount, currency, creation date, and user information.
    • transactions_list_Reply: An array of up to 10 summary objects, each containing:
      • id: Transaction platform ID
      • title: Status details (e.g., sender's name)
      • description: Reason or summary of the transaction (for "request" types, this includes the requested amount, currency, and a human-readable date)

Example output structure:

{
  "transactions": [
    {
      // Full transaction object with various properties
    }
  ],
  "transactions_list_Reply": [
    {
      "id": "12345",
      "title": "John Doe",
      "description": "Request 100 USD Today at 2:00 PM"
    }
  ]
}

Dependencies

  • External Service: Requires access to the Numi API via the PartnerServiceFactory.
  • Credentials: Needs a configured n8n credential named numiKeyApi.
  • Node Package: Uses the moment library for date formatting.

Troubleshooting

  • Missing or Invalid Credentials:
    Error: Authentication errors if the numiKeyApi credential is not set or invalid.
    Resolution: Ensure the correct API key is configured in n8n credentials.

  • Required Field Not Provided:
    Error: If "User Phone Number" is empty, the node will fail.
    Resolution: Always provide a valid phone number.

  • No Transactions Returned:
    Possible Cause: No transactions match the selected filters.
    Resolution: Adjust the "Types" and "Status" filters or verify the phone number.

  • Unexpected Output Structure:
    Cause: Changes in the Numi API response format.
    Resolution: Check for updates to the node or API documentation.

Links and References

Discussion