Actions5
Overview
This node integrates with the TANSS API to manage employee data, specifically focusing on technicians when using the "Techniker auflisten" (List Technicians) operation. It retrieves a list of all technicians registered in the TANSS system. This is useful for workflows that need to access or process technician information, such as scheduling, dispatching, or reporting.
Practical example:
A service company could use this node to automatically fetch all available technicians from their TANSS system and then assign jobs or send notifications based on the retrieved list.
Properties
| Name | Meaning |
|---|---|
| API Token | API token obtained from TANSS authentication, used to authorize requests to the API. |
Output
The node outputs an array of JSON objects, each representing a technician retrieved from the TANSS API. The exact structure depends on the API response but typically includes technician details such as ID, name, role, contact information, and status.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the TANSS API.
- Needs an API token credential for authentication, which must be provided via the "API Token" property.
- The base URL for the TANSS API is configured in the node credentials (not shown here).
Troubleshooting
Missing Credentials Error:
If no API credentials are found, the node will throw an error: "Keine Anmeldedaten gefunden!" (No login data found!). Ensure that the required API key credential is properly set up in n8n.Empty Response or No Technicians:
If the API returns an empty list, verify that there are technicians registered in the TANSS system and that the API token has sufficient permissions.API Request Failures:
Errors during the request will be reported with messages like "Fehler beim Ausführen von getTechnicians: [error message]". Check network connectivity, API token validity, and API endpoint availability.Invalid Operation:
If an unsupported operation is selected, the node throws an error indicating the operation is not recognized.
Links and References
- TANSS API Documentation (please 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/