Actions11
Overview
This node interacts with the PerfexCRM API to retrieve multiple tickets based on specified filters and limits. It is useful for scenarios where you need to fetch a list of support or service tickets from your CRM system, such as generating reports, monitoring ticket statuses, or integrating ticket data into other workflows.
For example, you can use this node to:
- Retrieve all open tickets in a specific department.
- Fetch a limited number of high-priority tickets assigned to a customer.
- Get tickets filtered by status and priority for analysis or notification purposes.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all matching tickets or only up to a specified limit. |
| Limit | Maximum number of tickets to return when "Return All" is false (minimum 1, default 50). |
| Filters | Collection of filters to narrow down the tickets: |
| - Status | Filter tickets by their status. Options: All, Open, In Progress, Answered, On Hold, Closed. |
| - Department | Filter tickets by department ID. |
| - Priority | Filter tickets by priority. Options: All, Low, Medium, High, Urgent. |
| - Customer ID | Filter tickets by a specific customer ID. |
Output
The output is an array of JSON objects representing tickets retrieved from the PerfexCRM API. Each object contains the ticket's details as provided by the API, including fields like subject, status, priority, department, customer ID, and other relevant ticket information.
No binary data is output by this operation.
Dependencies
- Requires an API key credential for authenticating with the PerfexCRM API.
- The node uses the base URL and API version from the credentials to construct requests.
- Network access to the PerfexCRM API endpoint is necessary.
Troubleshooting
- Common issues:
- Incorrect or missing API credentials will cause authentication failures.
- Using invalid filter values (e.g., non-existent department IDs) may result in empty results or errors.
- Exceeding API rate limits could lead to request failures.
- Error messages:
- Authentication errors typically indicate invalid or expired API keys; verify and update credentials.
- Validation errors may occur if filter parameters are malformed; ensure correct types and values.
- Network errors suggest connectivity problems; check internet access and API endpoint availability.
Links and References
- PerfexCRM API Documentation (for detailed API endpoints and parameters)
- n8n documentation on HTTP Request Node (similar request handling)