Tulz is not an island. Stock comes in by CSV, reports go out as Excel, inspection dates land in the calendar, events trigger webhooks, and anyone using Microsoft 365 or Google Workspace signs in with it.
For the workshop software there is the job number on every check-out and a JSON API through which other programs read and book tools – with keys that may do only what they should.
How it works in the workshop
- Import stock – CSV with tools, parts and storage locations; columns are mapped, errors shown before the import (CSV import).
- Connect sign-in – Microsoft Entra or Google Workspace; accounts are linked on first sign-in (Webhooks, SSO and language).
- Set up webhooks – on check-out, return, damage or inspection Tulz calls your address, signed and with retries on failure (Setting up a webhook).
- Use the API – create keys with scope (read, book) and site binding, query tools and book check-outs.
What comes with it
- Calendar subscription (ICS) for inspection dates in Outlook, Google or Apple Calendar (Calendar subscription)
- Excel and CSV export of all lists and reports
- Job number on every check-out as the bridge to the workshop software
- MQTT for the cabinet control, ZPL for label printers
- Tool dealers' catalogues for the set library
Who it is for
Businesses with existing workshop software, groups with central IT – and dealers and manufacturers who want to contribute their catalogues.
Frequently asked questions
Is there an interface to my workshop software?
Via the job number and the JSON API any software that handles web interfaces can be connected. Ready-made connections for individual programs appear as soon as their makers provide an interface.
What can I import by CSV?
Tools with all numbers, parts of sets, storage locations, categories and users. A template with all columns is available to download.
Are webhooks secured?
Every message is signed, only HTTPS targets are allowed, and on failure Tulz retries delivery.