Actions5
Overview
This node integrates with the TANSS API to manage employee data. It supports operations such as creating a new employee, retrieving employee details, listing all technicians, updating employee information, and fetching availability data for an employee.
Typical use cases include:
- Automating employee record creation or updates in TANSS from other systems.
- Synchronizing employee data between TANSS and external HR or scheduling tools.
- Retrieving technician lists for dispatching or workload management.
- Checking employee availability for planning purposes.
For example, you could use this node to update an employee’s contact details automatically when they change in your HR system, or to fetch all technicians currently registered in TANSS for assignment in a service workflow.
Properties
| Name | Meaning |
|---|---|
| API Token | API token obtained from TANSS authentication, used to authorize requests. |
| Mitarbeiter-ID | The unique identifier of the employee to retrieve, update, or get availability for. |
| Mitarbeiterfelder | A collection of employee fields to create or update, including: |
| - Vorname (First name) | |
| - Nachname (Last name) | |
| - E-Mail (Email address) | |
| - Telefon (Phone number) | |
| - Abteilungs-ID (Department ID) | |
| - Rolle (Role): Administrator, Techniker, Benutzer, Manager | |
| - Aktiv (Active): Boolean indicating if the employee is active |
The Operation property (not listed here but implied) determines which action is performed: createEmployee, getEmployee, getTechnicians, updateEmployee, or getAvailability.
Output
The node outputs JSON data corresponding to the response from the TANSS API for each operation:
- For createEmployee and updateEmployee, the output contains the created or updated employee object.
- For getEmployee, it returns the detailed employee data.
- For getTechnicians, it returns a list/array of technician employees.
- For getAvailability, it returns availability information related to the specified employee.
No binary data is produced by this node.
Dependencies
- Requires an API token credential for authenticating with the TANSS API.
- The base URL for the TANSS API is provided via credentials.
- The node uses HTTP requests to communicate with the TANSS backend endpoints.
Troubleshooting
- Missing Credentials: If no API token credential is found, the node throws an error "Keine Anmeldedaten gefunden!" Ensure that the API token is correctly configured in the node credentials.
- Empty Fields on Create/Update: When creating or updating an employee, if no fields are provided, the node throws errors like "Keine Felder für die Mitarbeitererstellung angegeben." or "Keine Felder zum Aktualisieren angegeben." Always provide at least one field to create or update.
- Unknown Operation: If an unsupported operation is selected, the node will throw an error indicating the operation is not recognized.
- API Request Failures: Errors during HTTP requests return messages prefixed with "Fehler beim Ausführen von [operation]:". Check network connectivity, API token validity, and endpoint availability.
Links and References
- TANSS API Documentation (not provided here; consult your TANSS API provider)
- n8n HTTP Request Node documentation for understanding request options: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/