Actions6
Overview
This node interacts with the TANSS API to retrieve various lists of tickets related to a company or employees. Specifically, the "Get Own Tickets" operation fetches tickets assigned to the current employee authenticated by the provided API token. This is useful for technicians or employees who want to view their personal ticket assignments directly within an n8n workflow.
Practical examples include:
- A technician automating daily reports of their assigned tickets.
- Integrating ticket data into other systems like CRM or project management tools.
- Monitoring and alerting on new or updated tickets assigned to oneself.
Properties
| Name | Meaning |
|---|---|
| API Token | API token obtained from the TANSS API login; used to authenticate requests to the API. |
Output
The node outputs an array of JSON objects representing the tickets assigned to the current employee. Each item in the output corresponds to the full response from the TANSS API endpoint /backend/api/v1/tickets/own. The exact structure depends on the API but typically includes ticket details such as ID, status, description, priority, and assignment information.
No binary data is output by this node.
Dependencies
- Requires access to the TANSS API with a valid API token credential.
- The node expects the base URL of the TANSS API to be configured in the credentials.
- Network connectivity to the TANSS API endpoint is necessary.
Troubleshooting
- No credentials returned!: This error occurs if the API token credential is missing or not properly configured. Ensure that the API token is correctly set up in the node's credentials.
- Failed to execute getOwnTickets: [error message]: Indicates a failure during the API request, possibly due to network issues, invalid token, or API downtime. Verify the API token validity and network access.
- The operation "..." is not recognized.: This error should not occur if using the predefined operations. It indicates an invalid operation parameter was passed.
Links and References
- TANSS API documentation (refer to your internal or official TANSS API docs for detailed ticket schema and authentication)
- n8n documentation on creating and using credentials and HTTP Request nodes