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 support requests, managing workload distribution, or integrating ticket information into other systems.
Specifically, the "Get Company Tickets" operation fetches all tickets associated with a specified company ID. This can help customer support teams or account managers quickly access and process tickets relevant to a particular client.
Practical example:
A user could set up this node in an n8n workflow to automatically pull all open tickets for a given company each morning, then send a summary email to the responsible team or update a dashboard.
Properties
| Name | Meaning |
|---|---|
| API Token | API token obtained from the TANSS API login; used to authenticate requests to the API. |
| Company ID | Numeric ID of the company for which to fetch tickets (only required for "Get Company Tickets" operation). |
Output
The node outputs an array of JSON objects, where each object contains the raw response from the TANSS API for the requested tickets. The structure of the JSON depends on the API's response but generally includes ticket details such as IDs, statuses, descriptions, assigned personnel, and timestamps.
No binary data output is produced by this node.
Dependencies
- Requires an active TANSS API credential with a valid API token.
- The node expects the base URL of the TANSS API to be configured within the credentials.
- Network access to the TANSS API endpoint is necessary.
Troubleshooting
- Missing Credentials Error: If no credentials are returned, ensure that the API token credential is properly configured and linked to the node.
- Invalid Operation Error: If an unrecognized operation is selected, verify that the operation name matches one of the supported options.
- API Request Failures: Errors during the API request (e.g., network issues, invalid token) will throw an error with the message
Failed to execute <operation>: <error message>. Check the API token validity, network connectivity, and that the company ID is correct. - Empty or Unexpected Response: If the API returns no tickets or unexpected data, confirm that the company ID exists and has associated tickets in the TANSS system.
Links and References
- TANSS API Documentation (refer to your internal or provided API docs for detailed endpoints and data structures)
- n8n Documentation: Creating Custom Nodes