Actions6
Overview
This node interacts with the TANSS API to retrieve various lists of tickets related to companies, projects, and 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 quickly access their personal ticket workload within the TANSS system.
Practical examples include:
- A technician wanting to see all tickets currently assigned to them.
- Automating daily reports of personal ticket statuses.
- Integrating ticket data into other workflows for task management or notifications.
Properties
| Name | Meaning |
|---|---|
| API Token | API token obtained from the TANSS API login; used to authenticate requests securely. |
Output
The node outputs an array of JSON objects where each object contains the response from the TANSS API endpoint for the requested tickets. For the "Get Own Tickets" operation, the json output field will contain the list of tickets assigned to the authenticated employee. The exact structure depends on the TANSS API but typically includes ticket details such as ID, status, description, priority, and related metadata.
No binary data output is produced by this node.
Dependencies
- Requires a valid API token credential for the TANSS API.
- The node expects the base URL of the TANSS API to be configured in the credentials.
- Network connectivity to the TANSS API endpoints is necessary.
Troubleshooting
Common issues:
- Missing or invalid API token will cause authentication failures.
- Incorrect base URL configuration in credentials can lead to request errors.
- Network issues may prevent successful API calls.
Error messages:
"No credentials returned!": Indicates that the required API token credential was not provided or could not be retrieved. Ensure the credential is set up correctly."Failed to execute getOwnTickets: <error message>": The API request failed. Check the error message for details, which might indicate network problems, invalid tokens, or API downtime."The operation \"<operation>\" is not recognized.": An unsupported operation was selected. Verify the operation name is correct.
Links and References
- TANSS API documentation (refer to your organization's internal or public API docs)
- n8n documentation on creating and using credentials: https://docs.n8n.io/credentials/
- n8n HTTP Request helper usage: https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/