TANSS Mitarbeiter icon

TANSS Mitarbeiter

Verwaltet Mitarbeiter in der TANSS API

Overview

This node integrates with the TANSS API to manage employee data and retrieve availability information. It supports multiple operations such as creating employees, fetching employee details, listing technicians, updating employee data, and specifically retrieving availability for an employee.

A common use case is automating HR or workforce management tasks by syncing employee records or checking technician availability directly from TANSS within an n8n workflow. For example, you could automatically update your internal system when an employee's availability changes or create new employee entries based on external triggers.

The "Verfügbarkeit abrufen" (Get Availability) operation fetches availability data for a specified employee, which can be useful for scheduling, dispatching, or resource planning scenarios.

Properties

Name Meaning
API Token API token obtained from TANSS authentication, required for all operations.
Mitarbeiter-ID (Employee ID) Numeric ID of the employee; required for operations that target a specific employee such as getting employee details, updating employee data, or retrieving availability.

Output

The node outputs JSON data corresponding to the response from the TANSS API for the selected operation:

  • For "Verfügbarkeit abrufen" (Get Availability), the output JSON contains the availability information of the specified employee.
  • For other operations, the output JSON reflects the respective employee or technician data returned by the API.

No binary data output is produced by this node.

Dependencies

  • Requires an active connection to the TANSS API via an API token credential.
  • The node expects the base URL of the TANSS API to be configured in the credentials.
  • No additional environment variables are needed beyond the API token credential.

Troubleshooting

  • Missing Credentials: If no API token credential is found, the node throws an error "Keine Anmeldedaten gefunden!" (No login data found!). Ensure the API token credential is properly set up.
  • Empty Fields for Create/Update: When creating or updating an employee, if no fields are provided, the node throws errors indicating missing data. Always provide at least one field to create or update.
  • Invalid Operation: If an unsupported operation is selected, the node will throw an error stating the operation is not recognized.
  • API Request Failures: Errors during API calls include the operation name and the original error message. Check network connectivity, API token validity, and correct employee IDs.
  • Employee ID Required: For operations like "Verfügbarkeit abrufen", ensure a valid employee ID is provided; otherwise, the API call will fail.

Links and References

Discussion