Actions6
Overview
This node interacts with the TANSS API to retrieve various types of ticket lists related to companies, projects, and employees. It is useful for automating workflows that require fetching ticket data from the TANSS system, such as monitoring open tickets, generating reports, or integrating ticket information into other systems.
Common scenarios include:
- Fetching all tickets assigned to a specific company.
- Retrieving general tickets not assigned to any employee.
- Getting tickets assigned to the current user or other technicians.
- Accessing tickets linked to projects.
- Handling tickets that are not identified with any company.
For example, a support team could use this node to automatically pull their own assigned tickets each morning to prioritize work, or a manager could fetch all project-related tickets to track progress.
Properties
| Name | Meaning |
|---|---|
| Operation | The type of ticket list to retrieve. Options: - Get Company Tickets - Get General Tickets - Get Not Identified Tickets - Get Own Tickets - Get Project Tickets - Get Technician Tickets |
| API Token | API token obtained from the TANSS API login, used for authenticating requests. |
| Company ID | (Only for "Get Company Tickets" operation) The numeric ID of the company whose tickets you want to fetch. |
Output
The node outputs an array of JSON objects, each containing the response from the TANSS API for the requested ticket list. The structure of the JSON depends on the API response but generally includes details about tickets such as ticket IDs, status, assigned employees, associated companies or projects, and other relevant metadata.
No binary data output is produced by this node.
Dependencies
- Requires access to the TANSS API endpoint.
- Requires an API token credential for authentication.
- The base URL for the TANSS API is retrieved from the configured credentials.
- Network connectivity to the TANSS API server is necessary.
Troubleshooting
No credentials returned!
This error occurs if the node cannot find the required API token credential. Ensure that the API token is correctly configured in the node's credentials section.Failed to execute [Operation]: [Error Message]
Indicates a failure during the HTTP request to the TANSS API. Possible causes include invalid API token, network issues, or incorrect parameters (e.g., invalid company ID). Verify the API token validity, check network connectivity, and confirm parameter correctness.The operation "[Operation]" is not recognized.
This error suggests an unsupported operation was selected. Confirm that the operation name matches one of the supported options.
Links and References
- TANSS API Documentation (please refer to your internal or official TANSS API docs for detailed endpoints and data structures)
- n8n Documentation: Creating Custom Nodes