Glassix icon

Glassix

Consume Glassix API (v.0.1.0)

Actions8

Overview

The "Glassix" n8n node, for the resource Tickets and operation List Tickets, retrieves a list of tickets from the Glassix API within a specified date range. This node is useful for automating workflows that require fetching support or service tickets, such as generating reports, monitoring ticket status, or integrating ticket data with other systems.

Practical examples:

  • Automatically pulling all open tickets created in the last week for reporting.
  • Syncing new or updated tickets into a CRM or project management tool.
  • Filtering tickets by state (e.g., only "Open" or "Pending") for escalation workflows.

Properties

Name Type Meaning
Since String From date and time. Format: dd/mm/yyyy hh:mm:ss:ff (UTC). Specifies the start of the date range for listing tickets.
Until String Until date and time. Format: dd/mm/yyyy hh:mm:ss:ff (UTC). Specifies the end of the date range for listing tickets.
Additional Fields Collection Optional fields to further filter or sort results:
- Ticket State (String): Filter tickets by state(s) (comma-separated: Open, Closed, Pending, Snoozed).
- Sort Order (Options: ASC/DESC): Sort by opened time.
- Page (String): For pagination; shows next 100 tickets if more than 100 exist. When supplied, no other query param is allowed.

Output

The node outputs a JSON array where each item represents a ticket retrieved from the Glassix API. The exact structure of each ticket object depends on the API response, but typically includes fields such as ticket ID, subject, state, creation date, etc.

Example output:

[
  {
    "id": "12345",
    "subject": "Customer inquiry",
    "state": "Open",
    "createdAt": "2024-06-01T10:00:00Z",
    ...
  },
  ...
]

Note: The actual fields may vary based on the Glassix API.

Dependencies

  • External Service: Requires access to the Glassix API.
  • API Credentials: You must configure the glassixApi credentials in n8n.
  • Environment: No special environment variables are required beyond standard n8n credential setup.

Troubleshooting

  • Invalid Date Format: Ensure the "Since" and "Until" fields use the correct format (dd/mm/yyyy hh:mm:ss:ff UTC). Incorrect formats may result in errors or empty results.
  • Missing Credentials: If the glassixApi credentials are not set up or are invalid, the node will fail to authenticate.
  • Pagination Issues: If you supply the "Page" parameter, do not include other query parameters; otherwise, the request may be rejected.
  • Common Error Messages:
    • "Authentication failed" – Check your API credentials.
    • "Invalid date/time format" – Verify the input format for date fields.
    • "Too many requests" – You may be hitting rate limits; try again later.

Links and References

Discussion