Overview
This node integrates with the TANSS API to manage contracts and offers. It allows users to create, retrieve, list, and update contracts and offers within the TANSS system. Typical use cases include automating contract creation workflows, updating contract details programmatically, or fetching offer data for further processing.
For example, a user can automate the creation of a new contract by providing relevant contract details such as title, amount, and dates, which helps streamline contract management without manual entry in the TANSS platform.
Properties
| Name | Meaning |
|---|---|
| API Token | API token from TANSS authentication used to authorize requests. |
| Vertragsfelder | Collection of contract or offer fields to set when creating or updating. Includes: |
| - Titel | Title of the offer or contract. |
| - Beschreibung | Description of the offer or contract. |
| - Unternehmen-ID | ID of the associated company. |
| - Betrag | Contract amount. |
| - Währung | Currency of the contract. Options: EUR, USD, CHF. |
| - Startdatum | Start date of the contract. |
| - Enddatum | End date of the contract. |
| - Status | Status of the contract. Options: Entwurf (Draft), Aktiv (Active), Abgeschlossen (Completed), Storniert (Cancelled). |
| Angebots-/Vertrags-ID | ID of the offer or contract, required for retrieving or updating specific entries. |
Output
The node outputs an array of JSON objects representing the response from the TANSS API for each input item processed. The structure depends on the operation:
- For creation operations (
createOffer,createContract), the output contains the newly created offer or contract data. - For retrieval operations (
getOffer), it returns the detailed data of the specified offer. - For listing operations (
listOffers), it returns an array of offers. - For update operations (
updateContract), it returns the updated contract data.
No binary data is produced by this node.
Dependencies
- Requires an active TANSS API endpoint URL configured in credentials.
- Requires an API token credential for authenticating requests.
- The node uses HTTP requests to communicate with the TANSS backend API.
Troubleshooting
- Missing Credentials: If no API token or credentials are provided, the node will throw an error "Keine Anmeldedaten gefunden!" (No login data found!). Ensure that valid credentials are configured.
- Empty Fields for Creation/Update: When creating or updating offers/contracts, if no fields are provided, the node throws errors like "Keine Felder für die Vertragserstellung angegeben." (No fields specified for contract creation). Always provide necessary fields.
- Invalid Operation: If an unsupported operation is selected, the node throws 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]:", helping identify which operation failed. Check network connectivity, API token validity, and request parameters.
Links and References
- TANSS API Documentation (not provided here; consult your TANSS API provider)
- n8n HTTP Request Node documentation for understanding underlying request mechanics: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/