Glassix icon

Glassix

Consume Glassix API (v.0.1.0)

Actions8

Overview

The Glassix node for n8n allows you to interact with the Glassix API. Specifically, when using the Tickets resource and the Add Tags operation, this node enables you to add one or more tags to a specified ticket in your Glassix system. This is useful for categorizing, organizing, or marking tickets for easier filtering and workflow automation.

Common scenarios:

  • Automatically tagging support tickets based on their content or source.
  • Adding workflow-specific labels to tickets as they move through different stages.
  • Integrating with other systems to synchronize ticket metadata.

Example:
When a new customer inquiry arrives, you can use this node to automatically add tags like "urgent" or "billing" to the corresponding ticket, making it easier for your team to prioritize and manage requests.

Properties

Name Type Meaning
Ticket Id Number Unique identifier for a ticket to which tags will be added.
Tags Collection (List of Tag Label) One or more tag labels to assign to the specified ticket. Each tag is a string value representing a label.

Output

  • The node outputs a json object containing the result of the Add Tags operation.
  • The structure typically includes confirmation that the tags were added, possibly echoing back the ticket ID and the list of tags applied.
  • If the API returns additional information (such as updated ticket details), these may also be included in the output.

Note:
If the node supports binary data output, it would only be relevant if the API returns files or attachments, which is not typical for an Add Tags operation.

Dependencies

  • External Service: Requires access to the Glassix API.
  • API Credentials: You must configure valid Glassix API credentials (glassixApi) in your n8n instance.
  • n8n Configuration: Ensure the Glassix node is installed and properly configured within your n8n environment.

Troubleshooting

Common Issues:

  • Invalid Ticket Id: If the provided Ticket Id does not exist, the API may return an error indicating the ticket was not found.
  • Missing or Invalid Tags: If no tags are provided, or if a tag label is invalid, the operation may fail.
  • Authentication Errors: Incorrect or missing API credentials will result in authentication failures.

Error Messages & Resolutions:

  • "Ticket not found": Verify the Ticket Id is correct and exists in your Glassix account.
  • "Unauthorized" or "Invalid credentials": Check your Glassix API credentials configuration in n8n.
  • "Tags field required": Ensure at least one tag label is provided in the Tags property.

Links and References

Discussion