Actions9
Overview
The "TANSS Support" node manages support entries and appointments via the TANSS API. It allows users to create, update, retrieve, search, list, analyze, and upload signatures for support records related to service tickets and employee activities.
This node is beneficial in scenarios where organizations need to automate or integrate their support management workflows, such as:
- Automatically creating or updating support logs after a service call.
- Retrieving detailed support information by ID.
- Searching support entries by customer name, content, or type.
- Analyzing support data grouped by type, employee, company, or month.
- Uploading digital signatures for completed support tasks.
Practical example: A service company could use this node to log support times and locations for technicians, filter support entries within a date range, and generate reports on support types or employee workloads.
Properties
| Name | Meaning |
|---|---|
| API Token | API token from TANSS authentication used to authorize requests. |
| Support-ID | Numeric ID of the support entry to retrieve, update, or upload a signature for. |
| Support-Felder | Collection of fields for creating or updating a support entry, including: - Ticket-ID (number) - Date (timestamp) - Duration in minutes (number) - Location (Office, Customer, Remote) - Planning Type (Support, Appointment Proposal, Fixed Appointment, Vacation, Illness, Absence, Standby, Private Appointment, Overtime) - Employee ID (number) - Remitter ID (number) - Description text - Non-charged duration (minutes) - Cost center ID (number) - Support type ID (number) - Link type ID (number) - Link ID (number) |
| Operation | The action to perform, options include: - Support list retrieval - Get support by ID - Search by customer - Search by content - Search by type - Create support - Update support - Analyze support - Upload signature |
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 but generally includes support entry details such as IDs, timestamps, durations, descriptions, employee info, and other metadata.
No binary data output is produced by this node.
Dependencies
- Requires an API token credential for authenticating with the TANSS API.
- Needs network access to the configured TANSS API base URL.
- No additional external dependencies beyond the TANSS API.
Troubleshooting
- Missing credentials error: If no API token is provided or found, the node throws an error "Keine Anmeldedaten gefunden!" Ensure the API token is correctly set in the node credentials.
- Required parameter missing: For operations like searching by customer or updating support, if required parameters (e.g., customer name, support fields) are missing, the node throws errors indicating which field is missing. Provide all mandatory inputs.
- Invalid support ID: Using an invalid or non-existent support ID may cause API errors. Verify the ID before using it.
- API request failures: Network issues or incorrect API tokens can cause request failures. Check connectivity and token validity.
- Unsupported operation: If an unknown operation is selected, the node will throw an error stating the operation is not recognized.
Links and References
- TANSS API documentation (not provided here; consult your TANSS API provider)
- n8n documentation on creating custom nodes and handling API integrations: https://docs.n8n.io/
- General REST API usage best practices