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 is useful for automating business workflows that involve maintaining up-to-date company records or synchronizing company information between systems.
Practical examples include:
- Automatically creating new company entries in TANSS when a lead is converted in a CRM.
- Periodically updating company details based on external data sources.
- Retrieving company information to enrich other datasets or trigger notifications.
- Deleting obsolete company records as part of data cleanup processes.
- Fetching employee lists for reporting or HR automation.
Properties
| Name | Meaning |
|---|---|
| Operation | The action to perform: createCompany, getCompany, updateCompany, deleteCompany, getEmployees |
| API Token | API token from TANSS authentication (required for all operations) |
| Unternehmens-ID | Company ID (required for getCompany, updateCompany, deleteCompany, getEmployees) |
| Unternehmensfelder | Collection of company fields used for creation or update, including: - Name - Straße (Street and house number) - PLZ (Postal code) - Stadt (City) - Land (Country) - Telefon (Phone number) - E-Mail (Email address) - Website (Website URL) - Kategorie-ID (Category ID) - Typ-ID (Type ID) |
Output
The node outputs JSON data representing the response from the TANSS API for each executed operation:
- For createCompany: JSON object with the newly created company's details.
- For getCompany: JSON object with the requested company's data.
- For updateCompany: JSON object with the updated company information.
- For deleteCompany: JSON object confirming deletion status.
- For getEmployees: JSON array or object containing employees related to the specified company.
No binary data output is produced by this node.
Dependencies
- Requires an active TANSS API credential with a valid base URL and API token.
- The API token must be provided as an input property for each execution.
- Network access to the TANSS API endpoint is necessary.
- No additional external libraries beyond n8n's standard HTTP request helpers are required.
Troubleshooting
- Missing Credentials Error: If no credentials are found, the node throws an error "Keine Anmeldedaten gefunden!" Ensure the API token and base URL are correctly configured in the node credentials.
- Empty Fields for Create/Update: When creating or updating a company, if no company fields are provided, the node throws errors like "Keine Felder für die Unternehmenserstellung angegeben." or "Keine Felder zum Aktualisieren angegeben." Always provide at least one field to create or update.
- Invalid Operation: If an unsupported operation is selected, the node will throw an error indicating the operation is not recognized.
- API Request Failures: Errors during API calls return messages prefixed with "Fehler beim Ausführen von [operation]:". 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 (refer to your internal or official TANSS API docs)
- n8n HTTP Request Node documentation for understanding request options: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/
- General n8n node development guide: https://docs.n8n.io/integrations/creating-nodes/