Actions222
- Application Baseline Actions
- Attack Surface Actions
- Backup Software Actions
- EDR Actions
- Tags Actions
- PII Actions
- External Scan Actions
- Settings Actions
- Compliance Assessment Actions
- Reports Actions
- Compliance Actions
- Jobs Actions
- Active Directory Actions
- Retrieve Ad Roles
- Retrieve Ad User Licenses
- Retrieve Azure Licenses
- Retrieve Azure Ad Logs
- Retrieve Azure Secure Score
- Retrieve Ad Password Policies
- Retrieve Ad Groups View
- Retrieve Ad Ous View
- Retrieve Ad Gpos View
- Retrieve Ad Computers View
- Retrieve Ad Users View
- Retrieve Ad Domain Details
- Retrieve Ad Gpos Details
- Retrieve Get Ous Details
- Retrieve Get Groups Details
- Retrieve Ad Group Users
- Retrieve Ad Group Computers
- Retrieve Get User Details
- Retrieve Get Computer Details
- Retrieve Ad Roles Details
- Retrieve Ad Roles Member
- Retrieve Ad Basic Info
- Audit Log Actions
- Ad Audit Actions
- Asset Data Actions
- Retrieve Bios Info
- Retrieve Bio Info
- Retrieve Browser Extensions
- Retrieve Browser Extension
- Retrieve Ciphers View
- Retrieve Cipher View
- Retrieve Windows Protection Status
- Retrieve Window Protection Status
- Retrieve Asset Compliance Report Card
- Retrieve Asset Firewall Policy
- Retrieve Asset Installed Drivers
- Retrieve Asset Installed Driver
- Retrieve Asset Interface
- Retrieve Asset Msdt
- Retrieve Asset Ports
- Retrieve Asset Port
- Retrieve Asset Security Report Data
- Retrieve Asset Security Report Datum
- Retrieve Asset Shares
- Retrieve Asset Share
- Retrieve Asset Storages
- Retrieve Asset Storage
- Retrieve Asset Unqouted Services
- Retrieve Asset Unqouted Service
- Retrieve Asset User Shares
- Retrieve Asset User Share
- Retrieve Asset Video Info
- Retrieve Asset Windows Reboot Required
- Retrieve Asset Window Reboot Required
- Vulnerabilities Actions
- Firewall Actions
- Integration Actions
- Retrieve Integration Credentials
- Retrieve Integration Credential
- Create Integration Credential
- Update Integration Credential
- Delete Integration Credential
- Retrieve Integration Rules
- Retrieve Integration Rule
- Create Integration Rule
- Update Integration Rule
- Delete Integration Rule
- Retrieve Company Mappings
- Retrieve Company Mapping
- Create Company Mapping
- Update Company Mapping
- Delete Company Mapping
- Event Set Actions
- Ticket Template Actions
- Scheduler Actions
- Credentials Actions
- Asset Actions
- Retrieve Records
- Retrieve Assets
- Retrieve Asset
- Create Asset
- Update Asset
- Delete Asset
- Retrieve Asset Stats
- Retrieve Asset Stat
- Retrieve Asset View
- Retrieve Cron Jobs
- Retrieve Kernel Modules
- Retrieve Suid Permissions
- Retrieve Ufw Firewall Rules
- Retrieve Selinux Settings
- Retrieve Asset Iptables Rules
- Retrieve Asset Users
- Retrieve Asset Processes Running
- Retrieve Asset Services
- Retrieve Asset Patches Info
- Retrieve Asset Firewall Rules
- Retrieve Asset Registry Misconfiguration
- Retrieve Asset Open Ports
- Retrieve Notification Tickets View
- Retrieve System Events View
- Discovery Settings Actions
- Retrieve Discovery Settings
- Retrieve Discovery Setting
- Create Discovery Setting
- Update Discovery Setting
- Delete Discovery Setting
- Retrieve Agent Discoverysettings Mapping
- Retrieve Agent Discoverysetting Mapping
- Create Agent Discoverysetting Mapping
- Update Agent Discoverysetting Mapping
- Delete Agent Discoverysetting Mapping
- Auth Actions
- Company Actions
- Agent Actions
Overview
This node operation, Retrieve Custom Ticketing Template, is designed to fetch custom ticket templates from a ticketing system via an API. It allows users to specify query parameters such as conditions, pagination (skip and limit), and ordering to tailor the retrieval of ticket templates according to their needs.
Common scenarios where this node would be beneficial include:
- Integrating with a ticketing platform to dynamically load ticket templates for use in automated workflows.
- Filtering ticket templates based on specific criteria or user roles.
- Paginating through large sets of ticket templates to process or display them incrementally.
For example, a support automation workflow might retrieve only active ticket templates relevant to a particular user or department by setting appropriate query conditions and user ID headers.
Properties
| Name | Meaning |
|---|---|
| X USER ID | User Id header required for authentication or identification purposes in the API call. |
| Condition | Query condition string to filter which ticket templates to retrieve. |
| Skip | Number of records to skip for pagination purposes. |
| Limit | Maximum number of ticket templates to return. |
| Order By | Field name(s) to order the results by. |
Output
The node outputs JSON data representing the retrieved ticket templates matching the specified query parameters. The structure typically includes an array of ticket template objects, each containing details defined by the external ticketing system's API schema.
If the API supports binary data (e.g., attachments within templates), the node would handle it accordingly, but based on the provided code and properties, the output focuses on JSON data.
Dependencies
- Requires an API key or token credential configured in n8n to authenticate requests to the ticketing system.
- Depends on the external ticketing system's API endpoint that supports querying ticket templates with the specified headers and query parameters.
- No additional external libraries beyond those bundled with n8n and the OpenAPI integration are explicitly required.
Troubleshooting
- Missing or invalid X USER ID: The API may reject requests without a valid user ID header. Ensure the "X USER ID" property is correctly set.
- Invalid query conditions: Malformed or unsupported query strings in the "Condition" property can cause errors or empty results. Verify the syntax matches the API's expected format.
- Pagination issues: Setting "Skip" or "Limit" incorrectly (e.g., negative numbers) may lead to unexpected results or errors.
- Authentication failures: Ensure the API credentials are valid and have sufficient permissions to access ticket templates.
- Empty responses: If no templates match the query, the output will be empty; adjust filters or verify data availability.
Links and References
- Refer to your ticketing system’s API documentation for details on supported query parameters, authentication methods, and response formats.
- n8n documentation on HTTP Request node for understanding how headers and query parameters are sent.
- General best practices for API pagination and filtering.