Genex

Interact with Genex API

Actions18

Overview

The "Update Customer Flags" operation in the Genex n8n node allows you to update a set of boolean flags for a specific customer, identified by their customer number. This is useful in scenarios where you need to programmatically manage or synchronize customer status indicators, preferences, or eligibility flags within the Genex system from automated workflows.

Practical examples:

  • Automatically enabling or disabling certain features for a customer based on external triggers.
  • Batch updating customer flags as part of a data migration or integration process.
  • Setting or clearing flags in response to customer support actions or account changes.

Properties

Name Meaning
Customer Number Must be a valid Genex customer number. Identifies which customer's flags to update.
Flag 1 Boolean flag (true/false) to set or clear the first customer flag.
Flag 2 Boolean flag (true/false) to set or clear the second customer flag.
Flag 3 Boolean flag (true/false) to set or clear the third customer flag.
Flag 4 Boolean flag (true/false) to set or clear the fourth customer flag.
Flag 5 Boolean flag (true/false) to set or clear the fifth customer flag.
Flag 6 Boolean flag (true/false) to set or clear the sixth customer flag.
Flag 7 Boolean flag (true/false) to set or clear the seventh customer flag.
Flag 8 Boolean flag (true/false) to set or clear the eighth customer flag.
Flag 9 Boolean flag (true/false) to set or clear the ninth customer flag.

Output

  • The output will be a JSON object reflecting the result of the update operation. The structure typically includes:
    • Confirmation of the updated flags and customer number.
    • Any error messages if the update failed.
    • Additional metadata returned by the Genex API.

Example output:

{
  "CustomerNumber": 12345,
  "Flag1": true,
  "Flag2": false,
  "Flag3": true,
  "Flag4": false,
  "Flag5": false,
  "Flag6": false,
  "Flag7": false,
  "Flag8": false,
  "Flag9": false,
  "status": "success"
}

Note: Actual output fields may vary depending on the Genex API's response.

Dependencies

  • External Service: Requires access to the Genex API.
  • API Credentials: You must configure genexApi credentials in n8n.
  • n8n Configuration: No additional configuration required beyond setting up credentials.

Troubleshooting

Common issues:

  • Invalid Customer Number: If the provided customer number does not exist, the operation will fail.
  • Missing Credentials: If genexApi credentials are not configured, the node will throw an authentication error.
  • API Connectivity Issues: Network problems or incorrect API endpoint configuration can cause connection errors.

Error messages and resolutions:

  • "Must be a valid Genex customer number": Ensure the customer number exists in Genex.
  • "Authentication failed": Check that your genexApi credentials are correct and active.
  • "Network error" or "Unable to reach Genex API": Verify network connectivity and Genex API availability.

Links and References

Discussion