Overview
This node manages contracts and offers via the TANSS API. It supports creating, retrieving, listing, and updating contract and offer data. Typical use cases include automating contract lifecycle management, synchronizing contract details with external systems, or integrating offer creation into workflows.
For example, you can:
- Create a new contract with specified details like title, amount, and status.
- Update an existing contract’s fields such as start/end dates or status.
- Retrieve details of a specific offer by its ID.
- List all available offers.
This node is beneficial for businesses that need to automate contract handling processes or integrate contract data into broader automation workflows.
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"). |
| Vertragsfelder | Collection of contract or offer fields to create 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 executed operation. This includes:
- For creation operations (
createOffer,createContract): The newly created offer or contract object with all its properties. - For retrieval operations (
getOffer): The detailed data of the requested offer. - For listing (
listOffers): An array of offers. - For update (
updateContract): The updated contract object reflecting the changes.
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.
- Network access to the TANSS API endpoints is necessary.
Troubleshooting
- Missing Credentials: If no API token credential is provided, the node throws an error "Keine Anmeldedaten gefunden!" (No login data found!). Ensure the API token is configured correctly.
- Empty Fields on Create/Update: When creating or updating offers/contracts, if no fields are provided, the node throws errors like "Keine Felder für die Angebotserstellung angegeben." (No fields specified for offer creation) or "Keine Felder zum Aktualisieren angegeben." (No fields specified for updating). Always provide at least one field in the collection.
- 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]:". Check network connectivity, API token validity, and correct IDs.
Links and References
- TANSS API Documentation (not provided here; consult your TANSS API provider)
- n8n Documentation on Creating Custom Nodes: https://docs.n8n.io/integrations/creating-nodes/