Numi Resume Profile icon

Numi Resume Profile

Numi Resume Profile Node
Join our community

Overview

The Numi Resume Profile node retrieves a comprehensive profile summary for a user based on their phone number. It can optionally fetch and paginate the user's contacts, payment methods, and transaction history, with filtering options for transaction type and status. This node is useful in scenarios where you need to aggregate a user's financial and contact data from the Numi platform for reporting, analytics, or integration with other systems.

Practical examples:

  • Enriching CRM records with up-to-date user profiles, including recent transactions and contacts.
  • Automating KYC (Know Your Customer) processes by fetching payment methods and transaction histories.
  • Building dashboards that display a user's activity and connections within the Numi ecosystem.

Properties

Name Meaning
User Phone Number An user phone number to obtain resume profile. Required.
Get Contacts Enable to get contacts data. If true, the node will retrieve the user's contacts.
Paginate Contacts Pagination for contacts. "0" for all, "1" for first 10 contacts, "2" for first 20 contacts, etc.
Get Payment Methods Enable to get payment methods data. If true, the node will retrieve the user's payment methods.
Paginate Payment Methods Pagination for payment methods. "0" for all, "1" for first 10 payment methods, "2" for first 20 payment methods, etc.
Get Transactions Enable to get payment transactions data. If true, the node will retrieve the user's transactions.
Types Filter for transaction types. Options: All (all transactions), Send (send transactions), Request (request transactions).
Status Filter for transaction status. Options: All, Complete, Expired, In_progress, Pending, WaitingSenderToBeChargedByCashload.
Paginate Transactions Pagination for transactions. "0" for all, "1" for first 10 transactions, "2" for first 20 transactions, etc.

Output

The node outputs a single item with a json field containing the following possible keys:

  • numi_profile: 

    {
  "exists": true,
  "profile": { /* user profile object as returned by the service */ }
}

    Indicates if the profile exists and includes the full user profile details.

  • contacts (if "Get Contacts" is enabled): 

    {
  "isEmpty": false,
  "total": 15,
  "total_show": 10,
  "contacts": [ /* array of contact objects */ ]
}
    • isEmpty: Whether the contacts list is empty.
    • total: Total number of contacts found.
    • total_show: Number of contacts included in this output (after pagination).
    • contacts: Array of contact objects.

  • nlp_contacts (if "Get Contacts" is enabled):
    An array of simplified contact representations:

    [
  { "fullName": "John Doe", "phoneNumber": "+123456789" },
  ...
]

  • payment_methods (if "Get Payment Methods" is enabled): 

    {
  "isEmpty": false,
  "total": 5,
  "total_show": 5,
  "payment_methods": [ /* array of payment method objects */ ]
}
    • isEmpty: Whether the payment methods list is empty.
    • total: Total number of payment methods found.
    • total_show: Number of payment methods included in this output (after pagination).
    • payment_methods: Array of payment method objects.

  • nlp_cards (if "Get Payment Methods" is enabled):
    An array of payment method names:

    ["Visa ****1234", "Mastercard ****5678"]

  • transactions (if "Get Transactions" is enabled): 

    {
  "isEmpty": false,
  "total": 20,
  "total_show": 10,
  "transactions": [ /* array of transaction objects */ ]
}
    • isEmpty: Whether the transactions list is empty.
    • total: Total number of transactions found.
    • total_show: Number of transactions included in this output (after pagination and filtering).
    • transactions: Array of transaction objects, possibly enriched with additional fields for "Request" type.

Note: The actual structure of profile, contacts, payment_methods, and transactions depends on the upstream service responses.

Dependencies

  • External Service: Requires access to the Numi partner API via the PartnerServiceFactory.
  • API Key: Needs valid credentials (numiKeyApi) configured in n8n.
  • Node Dependencies: Uses the moment library for date formatting.

Troubleshooting

Common issues:

  • Invalid or missing phone number: The node requires a valid phone number; otherwise, the profile lookup will fail.
  • Missing credentials: If the numiKeyApi credential is not set up or invalid, the node will not be able to connect to the Numi API.
  • Pagination values: Setting pagination to "0" returns all results, which may lead to large payloads and performance issues.
  • No data returned: If the user does not exist or has no contacts/payment methods/transactions, the corresponding arrays will be empty and isEmpty will be true.

Error messages:

  • Profile not found: Ensure the phone number is correct and registered in the Numi system.
  • Authentication failed: Check your numiKeyApi credentials in n8n.
  • Unexpected response format: The upstream API may have changed; check for updates or contact support.

Links and References

Discussion