Overview
This node integrates with the TANSS API to manage contracts and offers. It supports operations such as creating, retrieving, listing offers, and creating or updating contracts. This node is useful for automating contract and offer management workflows, such as syncing contract data from TANSS into n8n or generating new offers programmatically.
A practical example would be automatically listing all current offers in TANSS to display them in a dashboard or creating a new offer based on user input collected elsewhere in an automation.
Properties
| Name | Meaning |
|---|---|
| API Token | API token obtained from TANSS authentication, used to authorize requests to the API. |
Note: The node also internally uses these parameters (not requested but relevant for this operation):
- Operation: Fixed to "Angebote auflisten" (listOffers) for this context.
- Angebots-/Vertrags-ID: Used for specific offer or contract retrieval or update (not applicable here).
- Vertragsfelder: Collection of fields for creating or updating offers/contracts (not applicable here).
Output
The output is an array of JSON objects representing the response from the TANSS API for the list offers operation. Each item corresponds to an offer retrieved from the API, containing all available offer details as returned by the backend.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the TANSS API endpoint.
- Needs an API token credential from TANSS authentication to authorize API calls.
- The base URL for the TANSS API is provided via credentials configured in n8n.
- No additional external dependencies are required.
Troubleshooting
- Missing Credentials: If no API token credential is found, the node throws an error "Keine Anmeldedaten gefunden!" (No login data found!). Ensure the API token credential is properly set up in n8n.
- API Errors: Errors during API requests will throw messages like "Fehler beim Ausführen von listOffers:
". Check the validity of the API token and network connectivity. - Unrecognized Operation: If an unsupported operation is specified, an error indicating the operation is not recognized will occur.
- Empty Fields: For create or update operations, if required fields are missing, the node throws errors indicating no fields were provided. For listing offers, this does not apply.
Links and References
- TANSS API Documentation (not provided in code; consult your TANSS API provider)
- n8n Documentation on creating custom nodes: https://docs.n8n.io/integrations/creating-nodes/