Overview
The node "TANSS Verträge" manages contracts and offers via the TANSS API. It supports creating, retrieving, listing, and updating offers and contracts. This node is useful for automating contract lifecycle management within workflows, such as generating new offers/contracts, fetching existing ones, or updating contract details programmatically.
Practical examples:
- Automatically create a new contract when a customer signs up.
- Retrieve offer details to display or process further in a workflow.
- Update contract status or terms based on external events or approvals.
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 set or update. Includes: |
| - 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 (EUR, USD, CHF) | |
| - Startdatum: Contract start date | |
| - Enddatum: Contract end date | |
| - Status: Contract status (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 (
getOffer) and listing (listOffers), it returns the corresponding offer(s) data. - 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, the node throws errors like "Keine Felder für die Angebotserstellung angegeben." or "Keine Felder zum Aktualisieren angegeben." (No fields specified for creation/update).
- Invalid Operation: If an unsupported operation is selected, the node throws an error indicating the operation is not recognized.
- API Request Failures: Errors during HTTP requests to the TANSS API will be reported with messages prefixed by "Fehler beim Ausführen von [operation]:", helping identify which operation failed.
To resolve issues:
- Ensure valid API token credentials are configured.
- Provide all required fields when creating or updating.
- Verify the operation name is correct.
- Check network connectivity and API availability.
Links and References
- TANSS API documentation (not provided here; consult your TANSS API provider)
- n8n documentation on creating custom nodes and using credentials: https://docs.n8n.io/