Genex

Interact with Genex API

Actions18

Customer → Set External System Reference

AI-generated

Overview

This n8n node allows you to set an external system reference for a customer in the Genex system. It is designed for scenarios where you need to link or synchronize customer records between Genex and another external system by storing an identifier from that external system against a Genex customer record.

Common use cases:

  • Integrating Genex with CRM, ERP, or other business systems.
  • Keeping track of corresponding customer IDs between Genex and third-party platforms.
  • Automating data synchronization tasks where cross-referencing is required.

Example:
You have a customer in both Genex and Salesforce. You can use this node to store the Salesforce Customer ID as an external reference in Genex, enabling future automated lookups or updates.

Properties

Name Meaning
Customer Number Must be a valid Genex customer number. This identifies which customer record in Genex will be updated.
System Identifier for the external system (e.g., "Salesforce", "SAP"). These values are case sensitive and should be entered exactly as supplied.
External Reference The unique identifier from the external system. Genex does not validate this field; it expects it to match the identifier in the external system.

Output

The node outputs a JSON object reflecting the result of the operation. While the exact structure depends on the Genex API response, you can expect:

  • Confirmation of the update (success/failure).
  • Any error messages if the operation failed.
  • Echoed input parameters for traceability.

Note:
This node does not output binary data.

Dependencies

  • External Service: Requires access to the Genex API.
  • Credentials: You must configure genexApi credentials in n8n for authentication.
  • Environment: No special environment variables are required beyond standard n8n credential setup.

Troubleshooting

Common issues:

  • Invalid Customer Number: If the provided customer number does not exist in Genex, the operation will fail.
  • Case Sensitivity: The "System" value is case sensitive. Ensure it matches exactly as required by your integration.
  • Missing Credentials: If genexApi credentials are not configured, the node will throw an authentication error.
  • API Errors: Any errors returned by the Genex API (such as network issues or invalid parameters) will be surfaced as node errors.

Error messages and resolutions:

  • "Must be a valid Genex customer number": Double-check the customer number exists in Genex.
  • "Identifier for the system ... should be entered as supplied": Verify the spelling and casing of the system identifier.
  • Authentication errors: Ensure your genexApi credentials are correctly set up in n8n.

Links and References

Discussion