Numi Resume ProfileInstall

Overview

The Numi Resume Profile node retrieves a comprehensive profile summary for a user based on their phone number. It can optionally fetch the user's contacts, payment methods, and transaction history, with support for filtering and pagination. This node is useful in scenarios where you need to aggregate a user's financial and social 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 statuses.
• Building dashboards that display a user's network and financial activity.

Properties

Output

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

• numi_profile:

  • exists: Boolean indicating if the profile was found.
  • profile: The user's profile object as returned by the service.

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

  • isEmpty: Boolean, true if no contacts found.
  • total: Total number of contacts available.
  • total_show: Number of contacts included in this output (after pagination).
  • contacts: Array of contact objects.

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

  • Array of simplified contact objects with fullName and phoneNumber.

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

  • isEmpty: Boolean, true if no payment methods found.
  • total: Total number of payment methods available.
  • 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):

  • Array of payment method names.

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

  • isEmpty: Boolean, true if no transactions found.
  • total: Total number of transactions available.
  • total_show: Number of transactions included in this output (after filtering and pagination).
  • transactions: Array of transaction objects, possibly filtered by type and status.

Example Output Structure

{
  "numi_profile": {
    "exists": true,
    "profile": { /* user profile fields */ }
  },
  "contacts": {
    "isEmpty": false,
    "total": 15,
    "total_show": 10,
    "contacts": [ /* array of contact objects */ ]
  },
  "nlp_contacts": [
    { "fullName": "John Doe", "phoneNumber": "+123456789" }
  ],
  "payment_methods": {
    "isEmpty": false,
    "total": 3,
    "total_show": 2,
    "payment_methods": [ /* array of payment method objects */ ]
  },
  "nlp_cards": ["Visa", "MasterCard"],
  "transactions": {
    "isEmpty": false,
    "total": 25,
    "total_show": 10,
    "transactions": [ /* array of transaction objects */ ]
  }
}

Dependencies

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

Troubleshooting

• Common Issues:

  • Invalid or missing phone number: If the phone number is not provided or incorrect, the node will not be able to retrieve the profile.
  • Missing credentials: If the required API key is not set up in n8n, the node will fail to connect to the Numi service.
  • Pagination values: Setting pagination to "0" returns all items, which may lead to large payloads and performance issues.

• Error Messages:

  • Profile not found: Indicates the phone number does not correspond to any user in the system.
  • Authentication failed: Check your API key configuration in n8n.
  • Request timeout or network error: Ensure n8n has network access to the Numi API endpoint.

Links and References

• n8n Documentation
• Numi Platform (if public) (replace with actual link if available)
• Moment.js Documentation