Gladly icon

Gladly

Interact with Gladly API
Join our community

Actions57

Overview

This node updates customer information in the Gladly system. It is useful for scenarios where you need to modify existing customer profiles with new or corrected data, such as updating contact details, addresses, or custom attributes. For example, if a customer's phone number changes or they move to a new address, this node allows you to keep their profile up to date automatically.

Properties

Name Meaning
Name Customer's name (e.g., "Martha J Williams")
Image URL for an image that will appear as the customer's avatar
Address Customer's street address
Emails Customer's email addresses; expects a JSON array of objects with fields like normalized, original, and primary
Phones Customer's phone numbers; expects a JSON array of objects including normalized number, extension, region code, primary flag, etc.
External Customer Id Customer ID in your system of record for Customer Profiles linked to older Lookup Adaptors (cannot be set for newer adaptors)
Custom Attributes Organization-specific attributes defined by the Customer Profile Definition; expects a JSON object with key-value pairs

Output

The node outputs JSON data representing the updated customer profile as returned by the Gladly API. This typically includes all the fields sent in the update request along with any additional metadata or identifiers assigned by the system. The output does not include binary data.

Dependencies

  • Requires an API key credential for authenticating with the Gladly API.
  • The base URL for API requests is set to https://petstore3.swagger.io/api/v3 (likely a placeholder).
  • The node uses standard HTTP headers for JSON content (Accept: application/json, Content-Type: application/json).

Troubleshooting

  • Invalid JSON in Emails or Phones: Since these properties expect JSON strings, malformed JSON will cause errors. Ensure valid JSON formatting.
  • External Customer Id Restrictions: Attempting to set externalCustomerId for profiles linked to newer Lookup Adaptors will fail because the field is not supported.
  • API Authentication Errors: Missing or invalid API credentials will result in authentication failures.
  • Network or Endpoint Issues: If the base URL is incorrect or the Gladly API is unreachable, requests will fail.
  • Data Validation Errors: Sending improperly formatted or unsupported values for fields like phones or customAttributes may cause the API to reject the update.

Links and References

Discussion