NodePit Runner for KNIME
Easily Connect KNIME Analytics Platform and NodePit Runner
Take full control of your NodePit Runner instance, right from within KNIME. NodePit Runner for KNIME turns the complete NodePit Runner REST API into a ready-to-use set of KNIME nodes, so you can deploy, schedule, run, and monitor your KNIME workflows without writing a single line of API code. On top of that, it adds a full explorer (space) integration, letting you browse, upload, and download files on your NodePit Runner instance right from the KNIME Explorer, just like a mounted drive.
Whether you're managing a handful of scheduled workflows or orchestrating a whole fleet of production pipelines, NodePit Runner for KNIME gives you a no-code way to automate and scale your NodePit Runner deployment, self-hosted or cloud.
Requires an existing NodePit Runner instance.
🚀 Features
- 📁 Projects: Create, update, and organize the workflows you deploy to NodePit Runner
- 🧩 Environments: Configure execution environments, including Docker-based environments with custom images and build settings
- ⏱️ Schedules: Create, update, and manage recurring or one-off schedules, including Docker-based schedules
- ▶️ Runs: Trigger, retry, cancel, and monitor workflow runs, retrieve logs and statistics
- 📄 Files: Upload, download, and manage files in your NodePit Runner workspace
- 🗂️ Explorer integration: Browse, upload, and download files on NodePit Runner directly from the KNIME Explorer
- 👥 Users & Members: Manage users, members, and access tokens
- 🔐 Authentication: Log in with username/password, personal access tokens, or OAuth-connected apps
- 🔍 Search: Search across projects, environments, runs, and schedules
- 📊 Statistics: Retrieve usage and run statistics for reporting and monitoring
🎯 Why NodePit Runner for KNIME?
- ✅ No-code automation: manage your entire NodePit Runner deployment visually, without touching the REST API
- ✅ Save hours of manual work: deploy, schedule, and monitor workflows automatically, at scale
- ✅ Meta-automation: build KNIME workflows that manage other KNIME workflows, like CI/CD for your data pipelines
- ✅ One tool, full lifecycle: combine workflow orchestration with KNIME's data prep, ETL, and reporting in a single environment
- ✅ Built for scale: roll out self-service tooling, dashboards, and guardrails for your whole team's runner infrastructure
🌟 Example Use Cases
- Automatically deploy new workflow versions to NodePit Runner as part of a CI/CD pipeline
- Build a live KNIME dashboard showing the status of every scheduled workflow
- Programmatically spin up schedules and environments for new projects
- Automatically retry or clean up failed runs based on custom business logic
- Collect run statistics and logs for auditing, reporting, or capacity planning
- Give non-technical stakeholders a guided KNIME workflow to manage their own schedules
NodePit Runner for KNIME is free to use. All you need is a NodePit Runner account, self-hosted or cloud, to get started.
Questions, ideas, or feedback? We'd love to hear from you: mail@nodepit.com
Contact
VendorPhilipp Katz
AddressBienertstraße 33,01187 Dresden,Germany
Emailmail@nodepit.com
Websitehttps://nodepit.com
Content
NodePit Runner
Server
Node to configure the server endpoints
Authorize
Nodes for different authorization methods
User
Manage users of the NodePit Runner, including registration, login, and password recovery.
Project
Most activities on the Runner are organized within “projects” which allow users with different roles to collaborate.
Member
Manage members of a project. A “member” is a user who has certain access to a “project”.
Executor
Manage “Executors” which are responsible for running schedules. From an architectural perspective, executors are separate Docker services which connect to the API, execute a “Run” based on a “Schedule” and provide results. Executors are responsible for spawning workers, which are separate Docker containers to execute a “Run” - once finished, the worker is removed.
Settings
Manage global configuration such as email setup, license keys, etc.
Environment
Manage “Environments” which are the foundation for running “Schedules”. The Runner supports different types of environments, e.g. “Shell” for running shell scripts or “KNIME” for running KNIME workflows.
File
Manage, upload, and download files. Files can be e.g. uploaded by the user to supply scripts or workflows to a schedule, or provided by the Runner as artifacts which were generated during a “Run”.
Schedule
Schedules are one of the central parts for the Runner. A schedule defines the execution of a task (e.g. a shell script, a KNIME workflow, …) at a specified time (e.g. every Monday at 15:00) within an “Environment”. Once a schedule is started, it is represented as a “Run”.
Run
A “Run” is the exection of a “Schedule”. The run is started either automatically or manually and will then keep information about the execution, i.e. log output, statistics, status, and artifacts.
Statistics
Gather global statistics and metrics about the Runner and its usage, e.g. for monitoring and analytics purposes.
Access Token
Manage personal access tokens (PATs) for the current user. PATs can be used as an alternative to JWT for authenticating API requests and are useful for scripting and automation.
Misc
Various functionalities which do not fit into any other category.
Advanced
Nodes for advanced configuration
Nodes
Workflows
Installation
To use this product in KNIME, install the extension NodePit Runner for KNIME from the below update site:
A zipped version of the software site can be downloaded here.