Glassix icon

Glassix

Consume Glassix API (v.0.1.0)

Actions8

Overview

This n8n node allows you to interact with the Glassix API, specifically to set the state of a ticket. The "Set State" operation for the "Tickets" resource enables users to change the status of a ticket (e.g., Open, Closed, Pending). This is useful in automated workflows where ticket management and lifecycle updates are required, such as closing resolved tickets, reopening them based on customer replies, or marking them as pending for further action.

Practical examples:

  • Automatically close support tickets after an issue is resolved.
  • Move tickets to "Pending" when awaiting customer response.
  • Reopen tickets if a follow-up message is received.

Properties

Name Type Meaning
Ticket Id Number Unique identifier for a ticket. Used to specify which ticket's state should be updated.
Next State Options New state to apply to the ticket. Possible values: Closed, Open, Pending. Cannot be set to Snoozed here.
Additional Fields → Get Ticket Boolean If true, the updated ticket details will be included in the response.
Additional Fields → Send Ticket State Changed Message Boolean If true, sends a notification to the client indicating the ticket's state has changed.
Additional Fields → Enable Webhook Boolean If true, triggers a webhook event for this state change. If false, no event will be sent.

Output

The node outputs a json object containing the result of the state change operation. If "Get Ticket" is enabled, the output will include the full ticket details after the update. Otherwise, it may only confirm the success of the operation or provide minimal information about the ticket.

Example output structure:

{
  "success": true,
  "ticketId": 12345,
  "newState": "Closed",
  "ticket": {
    // ...full ticket details if 'Get Ticket' is true
  }
}

If binary data is ever output, it would represent ticket attachments or related files, but this operation does not appear to handle binary data directly.

Dependencies

  • External Service: Requires access to the Glassix API.
  • API Credentials: You must configure the glassixApi credentials in n8n for authentication.
  • Environment Variables: None specified, but ensure network access to the Glassix API endpoint.

Troubleshooting

Common issues:

  • Invalid Ticket Id: If the provided Ticket Id does not exist, the node may return an error indicating the ticket was not found.
  • Missing Required Fields: Omitting required fields like Ticket Id or Next State will cause validation errors.
  • Insufficient Permissions: If the API credentials lack permission to modify tickets, the operation will fail.
  • Webhook Not Triggering: If "Enable Webhook" is false, no webhook events will be sent; ensure this is set correctly for your workflow needs.

Error messages and resolutions:

  • "Ticket not found": Check that the Ticket Id is correct and exists in Glassix.
  • "Invalid state value": Ensure "Next State" is one of the allowed options (Closed, Open, Pending).
  • "Authentication failed": Verify that the glassixApi credentials are correctly configured in n8n.

Links and References

This summary is based on static analysis of the provided source code and property definitions.

Discussion