Overview
The "TANSS Verträge" node manages contracts and offers via the TANSS API. It supports creating, retrieving, listing, and updating contract and offer data. This node is useful for automating contract lifecycle management within workflows, such as generating new offers/contracts, fetching existing ones for review, or updating contract details based on external triggers.
Practical examples:
- Automatically create a new contract when a customer signs up.
- Retrieve an offer's details to send in an email.
- Update contract status after payment confirmation.
Properties
| Name | Meaning |
|---|---|
| API Token | API token from TANSS authentication used to authorize requests. |
| Angebots-/Vertrags-ID | ID of the offer or contract to retrieve or update (required for getOffer and updateContract operations). |
| Vertragsfelder | Collection of contract/offer fields to create or update, including: |
| - Titel | Title of the offer/contract. |
| - Beschreibung | Description of the offer/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). |
Output
The node outputs JSON data representing the response from the TANSS API for the selected operation. The structure depends on the operation:
- For creation operations (
createOffer,createContract), it returns the newly created offer or contract object. - For retrieval operations (
getOffer), it returns the specific offer data. - For listing (
listOffers), it returns an array of offers. - For updates (
updateContract), it returns the updated contract object.
No binary data output 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 obtained from the node credentials configuration.
- Network access to the TANSS API endpoints is necessary.
Troubleshooting
- Missing Credentials: If no API token is provided or credentials are missing, the node throws an error "Keine Anmeldedaten gefunden!" (No login data found).
- Empty Fields for Creation/Update: When creating or updating offers/contracts, if no fields are specified, errors like "Keine Felder für die Angebotserstellung angegeben." or "Keine Felder zum Aktualisieren angegeben." will occur. Ensure required fields are set.
- 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 include the operation name and the original error message, e.g., "Fehler beim Ausführen von updateContract:
". Check network connectivity, API token validity, and request payload correctness.
Links and References
- TANSS API documentation (not provided here, but recommended to consult for detailed API field definitions and usage).