Supportpal icon

Supportpal

Consume Supportpal REST API (v.1.2.4)

Actions22

Ticket → Get All

AI-generated

Overview

This node interacts with the Supportpal API to retrieve all tickets based on specified query parameters. It supports filtering tickets by various criteria such as filter ID, ticket number, department, brand, channel, status, priority, tags, user, user email, organisation, assigned operator, watching operator, and internal status. It also allows pagination and sorting of results. The node can return either a detailed or simplified response containing only the ticket data. This is useful for scenarios where users need to fetch and process multiple tickets from Supportpal for reporting, monitoring, or integration with other systems.

Use Case Examples

  1. Fetch all tickets assigned to a specific department and priority for analysis.
  2. Retrieve tickets filtered by user email and status for customer support workflows.
  3. Get a simplified list of tickets created within a certain range for quick overview.

Properties

Name Meaning
Simplify Response If true, returns a simplified response containing only the ticket data.
Query Parameters Collection of filters and options to refine the tickets retrieved, including filter ID, ticket number, department, brand, channel, status, priority, tag, user, user email, organisation, assigned operator, watching operator, internal flag, start index, limit, order column, and order direction.

Output

JSON

  • id - Unique identifier of the ticket.
  • subject - Subject or title of the ticket.
  • status - Current status of the ticket.
  • priority - Priority level of the ticket.
  • department - Department associated with the ticket.
  • user - User who submitted the ticket.
  • assigned - Operator assigned to the ticket.
  • created_at - Timestamp when the ticket was created.
  • updated_at - Timestamp when the ticket was last updated.
  • customfield - Custom fields associated with the ticket, if any.

Dependencies

  • Supportpal API with API key credential

Troubleshooting

  • Ensure the API credentials are correctly configured and have sufficient permissions to access ticket data.
  • Verify that the query parameters are correctly formatted, especially when using comma-delimited strings for multiple IDs.
  • If the node returns an error about missing or invalid parameters, check that required fields like filter operator are set when using private filters.
  • Network or API downtime may cause request failures; retry or check Supportpal service status.

Links

Discussion