Actions5
Overview
This node integrates with the TANSS API to manage company data. It supports creating, retrieving, updating, and deleting companies, as well as fetching employees associated with a company. This node is useful for automating business workflows that involve managing company records or employee lists within the TANSS system.
Practical examples include:
- Automatically adding new companies from form submissions.
- Synchronizing company details between TANSS and other systems.
- Retrieving employee lists for reporting or further processing.
- Cleaning up outdated company records by deleting them programmatically.
Properties
| Name | Meaning |
|---|---|
| API Token | API token obtained from TANSS authentication, used to authorize requests. |
Output
The node outputs JSON data corresponding to the response from the TANSS API for each operation:
- For createCompany, it returns the newly created company's data.
- For getCompany, it returns the details of the specified company.
- For updateCompany, it returns the updated company data.
- For deleteCompany, it returns confirmation of deletion (usually an empty or status message).
- For getEmployees, it returns a list of employees belonging to the specified company.
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 provided in the credentials configuration.
- Network access to the TANSS API endpoint is necessary.
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 is correctly configured.
- Empty Fields on Create/Update: When creating or updating a company, 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 return messages like "Fehler beim Ausführen von [operation]: [error message]". Check network connectivity, API token validity, and correct company IDs.
- Company ID Required: Operations other than creation require a valid company ID; ensure this is set properly.
Links and References
- TANSS API Documentation (not provided here, but users should refer to their official TANSS API docs for detailed endpoint info)
- n8n Documentation on HTTP Request Node and Credential Setup for API integrations