Actions6
Overview
This node interacts with the TANSS API to retrieve various lists of tickets related to companies, projects, technicians, or employees. It is useful for automating workflows that require fetching ticket data from the TANSS system, such as monitoring open issues, generating reports, or integrating ticket information into other systems.
Specifically, the "Get Project Tickets" operation fetches tickets associated with projects, enabling users to track project-related tasks or issues efficiently.
Practical example:
A project manager could use this node to automatically pull all tickets linked to ongoing projects and feed them into a dashboard or notification system to keep stakeholders updated on project progress and outstanding issues.
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 where each object contains the response from the TANSS API for the requested tickets. For the "Get Project Tickets" operation, the json field will contain the list of tickets associated with projects as returned by the API.
No binary data output is produced by this node.
Dependencies
- Requires access to the TANSS API endpoint.
- Requires an API token credential for authentication with the TANSS API.
- The base URL for the TANSS API is obtained from the node credentials configuration.
- The node uses HTTP GET requests with the API token included in the request headers.
Troubleshooting
- Missing Credentials Error: If no credentials are provided or found, the node throws an error indicating "No credentials returned!". Ensure that the API token and base URL are correctly configured in the node credentials.
- Unrecognized Operation: If an unsupported operation value is set, the node throws an error stating the operation is not recognized. Verify that the operation name matches one of the supported options.
- Request Failures: Network issues, invalid API tokens, or incorrect base URLs can cause request failures. The node will throw errors like
Failed to execute getProjectTickets: <error message>. Check network connectivity, validate the API token, and confirm the base URL is correct. - API Token Usage: The API token must be valid and have sufficient permissions to access the requested ticket data.
Links and References
- TANSS API Documentation (refer to your internal or official TANSS API docs for detailed endpoints and authentication)