Actions6
Overview
This node interacts with the TANSS API to retrieve various types of ticket lists related to companies, projects, technicians, and employees. It is useful for automating workflows that require fetching ticket data from the TANSS system, such as monitoring project progress, managing company support tickets, or tracking technician assignments.
For the "Get Project Tickets" operation specifically, the node fetches all tickets associated with projects. This can be beneficial in scenarios where a user wants to gather all project-related issues or tasks for reporting, analysis, or further processing within an automated workflow.
Example use cases:
- Automatically retrieving all project tickets to generate status reports.
- Integrating project ticket data into other systems like CRM or issue trackers.
- Monitoring project workload by analyzing ticket counts and details.
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, each containing the response from the TANSS API for the requested tickets. For the "Get Project Tickets" operation, the json output field contains the list of tickets associated with projects as returned by the API.
The exact structure of the ticket data depends on the TANSS API response but typically includes ticket details such as IDs, descriptions, statuses, assigned personnel, and related project information.
No binary data output is produced by this node.
Dependencies
- Requires access to the TANSS API endpoint.
- Needs an API token credential obtained from the TANSS API login.
- The base URL for the TANSS API is configured in the node credentials.
- Network connectivity to the TANSS API server must be available.
Troubleshooting
- Missing Credentials: If no API token or credentials are provided, the node will throw an error indicating missing credentials. Ensure the API token is correctly set.
- Invalid Operation: Selecting an unsupported operation will cause an error stating the operation is not recognized. Verify the operation name is correct.
- API Request Failures: Errors during the HTTP request (e.g., network issues, invalid token) will result in failure messages specifying which operation failed and why. Check API token validity, network connection, and API availability.
- Incorrect Company ID: Although not relevant for "Get Project Tickets," other operations requiring a company ID may fail if the ID is invalid or missing.
Links and References
- TANSS API Documentation (refer to your internal or official TANSS API docs for detailed endpoints and data structures)
- n8n Documentation on Creating Custom Nodes: https://docs.n8n.io/integrations/creating-nodes/