Gladly icon

Gladly

Interact with Gladly API
Join our community

Actions57

Overview

The "Update Answer" operation in the "Answer Management" resource allows users to modify an existing answer's details within a customer support or knowledge base system. This node is useful for keeping answers up-to-date, improving clarity, or changing the audience targeting of specific answers.

Typical use cases include:

  • Updating the title or name of a help article or canned response.
  • Modifying the description to provide agents with better context.
  • Changing which customer segments (audiences) can see the answer.

For example, if a password reset procedure changes, you can update the answer's name and description accordingly, ensuring agents always have the latest information.

Properties

Name Meaning
Answer Id The unique identifier of the answer to update. This is required to specify which answer will be modified.
Name The new customer-facing name/title of the answer.
Description A detailed description providing more information about the answer, visible to agents during search. Only applicable for email and messaging types.
Audience Ids A JSON array of audience IDs that should be associated with the answer. Updating this replaces all existing audience associations.

Output

The node outputs JSON data representing the updated answer object as returned by the API. This typically includes the updated fields such as the answer ID, name, description, and associated audience IDs.

No binary data output is indicated.

Dependencies

  • Requires access to the Gladly API endpoint for managing answers.
  • Needs an API authentication token or key configured in n8n credentials to authorize requests.
  • The base URL used in the bundled code is a placeholder (https://petstore3.swagger.io/api/v3), so it must be replaced with the actual Gladly API endpoint in production.

Troubleshooting

  • Invalid Answer Id: If the provided Answer Id does not exist, the API will likely return a "not found" error. Verify the ID before updating.
  • Malformed Audience Ids JSON: The Audience Ids property expects valid JSON. Improper formatting will cause parsing errors. Ensure the JSON array syntax is correct.
  • Missing Required Fields: The Answer Id is mandatory. Omitting it will prevent the update from proceeding.
  • API Authentication Errors: Ensure the API key or token is correctly set up in n8n credentials; otherwise, authorization failures will occur.
  • Unsupported Content Types: The Description field only applies to email and messaging content types. Using it with other types may have no effect or cause errors.

Links and References

Discussion