Actions6
Overview
This node interacts with the TANSS API to retrieve various types of ticket lists related to companies, projects, and employees. Specifically, for the "Get Project Tickets" operation, it fetches tickets associated with projects from the TANSS system. This is useful in scenarios where you want to automate workflows involving project-related issue tracking or reporting within TANSS.
Practical examples include:
- Automatically retrieving all tickets linked to projects to generate status reports.
- Integrating project ticket data into dashboards or other systems for monitoring.
- Triggering follow-up actions based on project ticket statuses.
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 field contains the list of tickets associated with projects as returned by the endpoint:
GET {baseURL}/backend/api/v1/tickets/projects
The exact structure of each ticket object depends on the TANSS API response but typically includes details such as ticket ID, description, status, assigned personnel, and project association.
No binary data output is produced by this node.
Dependencies
- Requires access to the TANSS API via a valid API token.
- The node expects credentials configured with the base URL of the TANSS API.
- Network connectivity to the TANSS API endpoint is necessary.
Troubleshooting
- Missing Credentials: If no credentials are provided or invalid, the node will throw an error indicating "No credentials returned!" Ensure that the API token and base URL are correctly configured.
- Invalid Operation: Selecting an unsupported operation will result in an error stating the operation is not recognized.
- API Request Failures: Errors during the HTTP request (e.g., network issues, invalid token) will cause the node to throw an error with the message "Failed to execute [operation]: [error message]". Verify the API token validity and network connectivity.
- Empty Responses: If the API returns no tickets, the output JSON array may be empty. Confirm that there are tickets associated with projects in the TANSS system.
Links and References
- TANSS API Documentation (refer to your internal or provided API docs for detailed ticket schema and authentication)
- n8n Documentation on HTTP Request Node (for understanding how API calls are made)