TANSS Mitarbeiter icon

TANSS Mitarbeiter

Verwaltet Mitarbeiter in der TANSS API

Overview

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

A common use case is automating HR or workforce management tasks by integrating TANSS employee data into workflows. For example, you can automatically fetch an employee’s availability before scheduling tasks or update employee records based on external inputs.

The "Verfügbarkeit abrufen" (Get Availability) operation retrieves availability data for a specified employee, which is useful for planning and resource allocation.

Properties

Name Meaning
API Token API token from TANSS authentication used to authorize requests to the TANSS API.
Mitarbeiter-ID (Employee ID) Numeric ID of the employee whose data or availability is being accessed or modified. Required for certain operations including "Verfügbarkeit abrufen".

Output

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

  • For "Verfügbarkeit abrufen", the output JSON contains the availability information of the specified employee.
  • For other operations, it returns employee data, lists of technicians, or confirmation of creation/update actions.

No binary data output is produced by this node.

Example output structure for availability might look like:

{
  "employeeId": 123,
  "availability": [
    {
      "date": "2024-06-01",
      "available": true,
      "timeSlots": ["08:00-12:00", "13:00-17:00"]
    },
    ...
  ]
}

Dependencies

  • Requires an active TANSS API credential with a valid base URL and API token.
  • The node expects the API token to be provided as an input property.
  • No additional external dependencies beyond the TANSS API and n8n core modules.

Troubleshooting

  • Missing Credentials: If no TANSS API credentials are found, the node throws an error "Keine Anmeldedaten gefunden!" (No login data found!). Ensure that the API credential is configured correctly in n8n.
  • Empty Fields for Create/Update: When creating or updating an employee, if no fields are provided, the node throws errors indicating missing fields. Always provide at least one field when performing these operations.
  • 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, helping identify issues such as invalid tokens, network problems, or incorrect employee IDs.

Links and References


If you need details on other operations or resources, feel free to ask!

Discussion