Back to Nodes

TANSS

Last updated Jul 28, 2026

n8n community node to use the TANSS API

46 Weekly Downloads
153 Monthly Downloads

Included Nodes

TANSS

Description

n8n-nodes-tanss

> [!WARNING]
> Before upgrading, check ![License: MIT](https://opensource.org/licenses/MIT)
![CodeFactor](https://www.codefactor.io/repository/github/buddiesd/n8n-nodes-tanss)

This is an n8n community node. It lets you use the TANSS API in your n8n workflows.
TANSS is a professional ticket and service management system for handling support tickets, customer communication, and internal processes.

n8n is a fair-code licensed workflow automation platform.

Contents

  • Installation
  • Operations
  • Credentials
  • Compatibility
  • Resources
  • ToDo list
  • Changelog
  • Breaking Changes
  • Disclaimer
  • Contributing
  • Installation

    For installation in n8n

    Follow the official installation guide in the n8n community nodes documentation.

    For Local Development

    This project is an n8n community node and must be run from source for local development.

    #### Prerequisites

  • Node.js (v22.20.0 recommended)
  • npm
  • #### 1. Clone the repository

    You can clone the repository anywhere on your system — it does not need to be inside the n8n directory.

    git clone https://github.com/BuddiesD/n8n-nodes-tanss.git
    cd n8n-nodes-tanss
    

    #### 2. Install dependencies

    npm install
    

    #### 3. Start development mode

    Run the node in development mode with live reloading:

    npm run dev
    

    This command uses n8n-node dev to build the node, start a local n8n instance, and automatically apply code changes during development.

    npm run dev is equivalent to running n8n-node dev directly.

    Development (Dev Container)

    To start n8n with the custom node, run: npm run dev

    Note: The first startup may time out because n8n is being downloaded and set up.

    Operations

    208 operations across 30 resources. Each resource’s operations and their parameters are documented in the docs/ directory.

    | Resource | Operations | Docs |
    | :— | :— | :— |
    | Activity Feed | 4 | docs/activityFeed.md |
    | Availability | 2 | docs/Availability.md |
    | Call | 9 | docs/calls.md |
    | Call User | 3 | docs/callsuser.md |
    | Callback | 5 | docs/Callback.md |
    | Chat | 10 | docs/chats.md |
    | Checklist | 12 | docs/Checklists.md |
    | Company | 4 | docs/Company.md |
    | Company Category | 10 | docs/CompanyCategories.md |
    | Component | 9 | docs/Components.md |
    | CPU | 5 | docs/CPUs.md |
    | Domain | 6 | docs/Domains.md |
    | Employee | 2 | docs/Employees.md |
    | HDD Type | 5 | docs/hddTypes.md |
    | IP | 4 | docs/ips.md |
    | Mail | 7 | docs/Mails.md |
    | Manufacturer | 5 | docs/manufacturers.md |
    | Operating System | 5 | docs/OperatingSystems.md |
    | PC | 5 | docs/PCs.md |
    | Periphery | 11 | docs/Periphery.md |
    | Project | 9 | docs/Projects.md |
    | Remote Support | 11 | docs/RemoteSupports.md |
    | Search | 1 | docs/Search.md |
    | Service | 5 | docs/services.md |
    | Software License | 16 | docs/SoftwareLicenses.md |
    | Ticket | 10 | docs/Tickets.md |
    | Ticket Content | 5 | docs/TicketContent.md |
    | Ticket List | 9 | docs/TicketLists.md |
    | Ticket State | 4 | docs/TicketStates.md |
    | Timestamp | 3 | docs/timestamp.md |

    For implementation status (done / testing / planned), see the ToDo list. For the full TANSS API reference, visit api-doc.tanss.de.

    Credentials

    Authentication is now fully credential-based and also works with n8n HTTP Request using TANSS credentials.

    Use the node parameter Auth Mode and select one credential type:

  • User Login (Auto Refresh)
  • – Credential: TANSS User API
    – Fields: Base URL, Username, Password, optional 2FA Secret
    – Automatically refreshes tokens using refreshToken when possible

  • Generated Token
  • – Credential: TANSS Generated Token API
    – Fields: Base URL, Generated API Token
    – Uses static generated token scopes (no refresh)

    Compatibility

    Compatible with n8n@1.60.0 or later
    Tested with TANSS API. Version: 10.15.0

    Resources

  • n8n community nodes documentation
  • Tanss API documentation
  • To-Do / Progress

    A detailed breakdown of all implemented and pending API endpoints is available in the ToDo list.

    Quick stats:

    | Metric | Value |
    | :— | :— |
    | Implemented | 208 |
    | ToDo | 363 |
    | Planned (Implemented + ToDo) | 571 |
    | Not Planned | 286 |
    | Completion | 36% |
    | Total API Endpoints | 857 |

    Disclaimer

    This is an unofficial, community-maintained project it is not affiliated with, endorsed by, or sponsored by TANSS or its parent company.

  • Trademarks: “TANSS” and all related names, logos, and product identifiers are trademarks of their respective owners. Their use here is purely descriptive and does not imply any official relationship.
  • Access requirement: Using this node requires a valid TANSS installation with appropriate API permissions. The authors are not responsible for providing or facilitating access to any TANSS system.
  • No warranty: This software is provided as-is, without any express or implied warranties. The authors make no guarantees regarding:
  • – Correctness or completeness of the API integration
    – Compatibility with specific TANSS versions

  • Liability: In no event shall the authors be held liable for any damages arising from the use of this software, including but not limited to data loss, service interruptions, or business disruptions.
  • Contributing

    Thank you for considering contributing to this project! Community contributions are what keep open-source projects growing and improving, and every contribution is highly appreciated.

    When submitting bug reports, please make sure they are:

  • Reproducible – clearly describe the steps required to reproduce the issue.
  • Detailed – include relevant information such as versions, environment, and setup.
  • Unique – avoid creating duplicate issues by checking existing ones first.
  • Focused – report one bug per issue to keep discussions clear and effective.