Overview
This node integrates with the TANSS API to manage contracts and offers. It allows users to create, retrieve, list, and update contract and offer data within the TANSS system. Typical use cases include automating contract creation workflows, updating contract statuses, retrieving offer details for processing, or listing all available offers for reporting or further automation.
For example, a user can automate the creation of a new contract by providing relevant contract details such as title, amount, and dates, then send this data directly to the TANSS API without manual entry. Similarly, retrieving an offer's details by its ID can be automated to feed into other systems or processes.
Properties
| Name | Meaning |
|---|---|
| API Token | API token from TANSS authentication used to authorize requests. |
| Vertragsfelder | Collection of fields describing the contract or offer. 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). |
Note: The "Vertragsfelder" property is required when creating or updating offers/contracts.
Output
The node outputs JSON data representing the response from the TANSS API for the requested operation. This includes:
- For creation operations (
createOffer,createContract): The newly created offer or contract object returned by the API. - For retrieval operations (
getOffer): The detailed data of the specified offer. - For listing operations (
listOffers): An array of offers. - For update operations (
updateContract): The updated contract object.
No binary data output is produced by this node.
Dependencies
- Requires an active TANSS API credential with a valid API token.
- The node expects the base URL of the TANSS API to be provided via credentials.
- Network access to the TANSS API endpoint is necessary.
Troubleshooting
- Missing Credentials: If no API credentials are found, the node will throw an error indicating missing login data. Ensure that the API token credential is configured correctly in n8n.
- Empty Fields on Create/Update: When creating or updating offers/contracts, if no contract fields are provided, the node throws an error. Always provide at least one field in the "Vertragsfelder" collection.
- Invalid Operation: If an unsupported operation is selected, the node will report it as unrecognized.
- API Request Failures: Errors during API calls will return messages including the operation name and the underlying error message. Check network connectivity, API token validity, and request payload correctness.
Links and References
- TANSS API Documentation (not provided here; consult your TANSS API provider)
- n8n Documentation: Creating Custom Nodes
- General REST API usage in n8n: HTTP Request Node