Genex

Interact with Genex API

Actions18

Overview

The "Search Customers" operation of the Genex custom n8n node allows users to search for customer records in the Genex system using a search string. This is useful for automating workflows that require looking up customers based on partial or full information, such as names, emails, or account numbers. Typical scenarios include verifying customer existence before creating new records, fetching customer details for support tickets, or filtering out cancelled customers from results.

Practical examples:

  • Automatically searching for a customer by name when a new support request is received.
  • Integrating with CRM systems to fetch and display customer data.
  • Filtering active customers for marketing campaigns.

Properties

Name Meaning
Search String The text to search for within customer records. Required.
Include Cancelled Whether to include cancelled customers in the search results. Boolean (true/false).

Output

  • The output will be an array of objects under the json field, each representing a customer record matching the search criteria.
  • Each object contains customer details as returned by the Genex API. The exact structure depends on the API response but typically includes fields like customer ID, name, status, and other relevant attributes.

Dependencies

  • External Service: Requires access to the Genex API.
  • Credentials: Needs a configured genexApi credential in n8n.
  • Environment: No special environment variables are required beyond standard n8n setup.

Troubleshooting

  • Common Issues:

    • Invalid Credentials: If the provided Genex API credentials are incorrect or missing, the node will fail to connect.
    • API Errors: If the Genex API returns an error (e.g., due to malformed search strings or server issues), the node will throw an error.
    • No Results: If the search string does not match any customers, the output will be an empty array.

  • Error Messages:

    • "Cannot create SOAP client": Indicates a problem with the WSDL file or network connectivity.
    • "Authentication failed": Check your Genex API credentials.
    • "Operation not found": Ensure the correct operation name is used and matches the Genex API specification.

    Resolution: Double-check credentials, ensure the Genex API is reachable, and verify input parameters.

Links and References

Discussion