TANSS Verträge icon

TANSS Verträge

Verwaltet Verträge und Angebote in der TANSS API

Overview

This node integrates with the TANSS API to manage contracts and offers. It supports creating, retrieving, listing, and updating offers and contracts within the TANSS system. Typical use cases include automating contract lifecycle management, generating new offers based on input data, fetching existing offer details for review, and updating contract information programmatically.

Practical examples:

  • Automatically create a new sales offer when a lead reaches a certain stage in your CRM.
  • Retrieve detailed information about an existing offer to display or process further.
  • List all current offers to generate reports or dashboards.
  • Create or update contracts based on finalized negotiations or changes in terms.

Properties

Name Meaning
Operation The action to perform. Options: "Angebot erstellen" (Create Offer), "Angebot abrufen" (Get Offer), "Angebote auflisten" (List Offers), "Vertrag erstellen" (Create Contract), "Vertrag aktualisieren" (Update Contract).
API Token API token from TANSS authentication used to authorize requests.
Angebots-/Vertrags-ID (Offer/Contract ID) Numeric ID of the offer or contract; required for "getOffer" and "updateContract" operations.
Vertragsfelder (Contract Fields) Collection of fields describing the offer or contract. Includes: Title, Description, Company ID, Amount, Currency (EUR, USD, CHF), Start Date, End Date, Status (Draft, Active, Completed, Cancelled). Required for create and update operations.

Output

The node outputs JSON data representing the response from the TANSS API for each executed operation. This includes details of created or retrieved offers/contracts or lists of offers. The output structure directly reflects the API's JSON response format.

No binary data is produced by this node.

Dependencies

  • Requires access to the TANSS API endpoint, configured via credentials that provide the base URL and an API key.
  • The user must supply a valid API token for each execution, which is sent as a header in API requests.
  • Network connectivity to the TANSS backend API is necessary.

Troubleshooting

  • Missing Credentials: If no credentials are found, the node throws an error indicating missing login data. Ensure the API credential is properly configured in n8n.
  • Empty Fields for Creation/Update: When creating or updating offers/contracts, if no fields are provided, the node raises an error. Make sure to specify at least one field in the "Vertragsfelder" collection.
  • Invalid Operation: Selecting an unsupported operation results in an error. Verify the operation name matches one of the supported options.
  • API Request Failures: Errors during API calls return messages including the operation name and the underlying error message. Check network connectivity, API token validity, and correct IDs.
  • Incorrect IDs: For operations requiring an offer or contract ID, providing zero or invalid IDs may cause API errors.

Links and References

Discussion