Actions9
Overview
This node integrates with the TANSS API to manage support entries and appointments. It allows users to retrieve, search, create, update, analyze, and upload signatures for support records within the TANSS system. This is useful in scenarios where organizations need to automate or streamline their support ticket handling, appointment scheduling, and reporting processes.
For example, a user can:
- Retrieve a specific support entry by its ID.
- Search support tickets by customer name or content keywords.
- Create new support entries with detailed fields like date, duration, location, and type.
- Update existing support entries.
- Analyze support data over a specified time frame grouped by various criteria.
- Upload signatures related to support entries.
Properties
| Name | Meaning |
|---|---|
| API Token | API token from TANSS authentication used to authorize requests. |
| Support-ID | ID of the support entry to retrieve, update, or upload a signature for. |
Additional properties relevant to other operations (not requested but shown for context):
| Name | Meaning |
|---|---|
| Operation | The action to perform on support entries (e.g., listSupports, getSupport, createSupport). |
| CustomerName | Customer or company name to search support entries by customer. |
| SearchText | Text to search within support descriptions. |
| SupportTypeId | ID of the support type to filter or search by. |
| AnalysisOptions | Options for analyzing support entries including date range and grouping criteria. |
| FilterOptions | Various filters for listing supports such as timeframe, locations, planning types, etc. |
| SupportFields | Fields for creating or updating support entries, e.g., ticket ID, date, duration, etc. |
Output
The node outputs an array of JSON objects representing the response from the TANSS API for each input item processed. The structure depends on the operation performed:
- For "getSupport" and similar retrieval operations, the output JSON contains the details of the support entry.
- For "listSupports" and search operations, the output JSON contains lists of support entries matching the criteria.
- For "createSupport" and "updateSupport", the output JSON reflects the created or updated support entry.
- For "uploadSignature", the output JSON confirms the success or failure of the upload.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the TANSS API endpoint.
- Needs an API token credential for authentication.
- The base URL for the TANSS API must be configured in the credentials.
- Uses HTTP methods GET, POST, PUT depending on the operation.
Troubleshooting
- Missing Credentials: If no API token or credentials are provided, the node throws an error "Keine Anmeldedaten gefunden!" (No login data found).
- Required Parameters Missing: Operations like searching by customer or support type require specific parameters; missing these will cause errors indicating which parameter is required.
- Invalid Operation: If an unsupported operation is selected, the node throws an error stating the operation is not recognized.
- API Request Failures: Network issues or invalid tokens may cause request failures with messages like "Fehler beim Ausführen von [operation]: [error message]". Verify API token validity and network connectivity.
- Empty Field Errors: Creating or updating support entries without specifying any fields results in errors prompting to provide necessary fields.
Links and References
- TANSS API Documentation (not provided here, but users should refer to official TANSS API docs for detailed endpoint info)
- n8n HTTP Request Node documentation for understanding request options and error handling
If you want me to extract details for another operation or resource, please let me know!