The library

The library is where you find toolkits to install. It’s a browsable catalogue inside your Jootle instance, kept fresh from the platform.

You don’t have to leave Jootle to install. You don’t have to download anything (unless you want to import a .jtf.json directly). You don’t have to configure files. The flow is: open the library, find a toolkit, install it.

Library status

The library is being populated as the Jootle team finishes packaging toolkits. Check the storefront from your instance — Tools → Library — for the current catalogue. This page will be updated as toolkits become available. If a toolkit you’re expecting isn’t showing yet, it isn’t ready to publish; ask your Jootle for status.

Opening the library

In the sidebar, find Tools → Library. The library view shows:

Featured toolkits. Curated picks for what most customers find useful first.
Categories. Productivity, content, finance, governance, personal, and so on.
Search. Type what you’re looking for.
Recently added. New toolkits that have shipped.

Each toolkit has a tile showing its name, a one-line description, and a badge for its source (Official or Community).

Toolkit sources

A toolkit’s badge tells you who maintains it:

Official. Built and maintained by Jootle.
Community. Built by someone else, submitted to the library, and reviewed.

We’re conservative about what makes it into the public library. Each community submission goes through review, and toolkits that include external connections (API keys, third-party services) get extra scrutiny.

A third source, Custom, exists for toolkits you (or your team) built for yourselves — these live in your instance, not the public library. See Building your own toolkits.

What a toolkit’s detail page tells you

Click any tile to see the detail page. It covers:

What it does. A short description of the use case.
What it adds. The specific sidebar entries, playbooks, entity types, widgets.
What it requires. Any external services you’d need (a Stripe account, a Calendar integration, etc.).
Source and version. Who built it and the toolkit version.
The bill-of-materials. A precise list of what gets added to your instance.

If you’re considering a toolkit, read its detail page before installing. Two minutes there saves “huh, that wasn’t what I expected” later.

The install flow

Installing is one click on the detail page. What happens:

The toolkit’s bundle is fetched from the library.
Your instance shows you a preview — what entity types it will add, what playbooks, what menu entries, any conflicts with toolkits already installed.
You confirm the install.
The toolkit’s components register with your instance: sidebar entries, playbooks, entity types, widgets.
The install completes. The new sidebar entry appears within seconds.

If the toolkit needs setup (e.g., paste an API key for an external service), a setup wizard runs after install.

You’re not asked to restart anything; your Jootle doesn’t need a refresh; you can start using the new capabilities immediately.

After installing: try one thing

After installing a toolkit, the best first move is to try one thing it adds. Don’t try to “learn the whole toolkit”; just use one feature.

The toolkit reveals itself as you use it. Most have onboarding walkthroughs on first open; those are worth following.

What can go wrong

Two cases worth knowing:

Toolkit conflicts. Rare. Two toolkits both want to claim the same entity slug (say note), for example. The preview dialog detects this before install and surfaces it; you decide whether to proceed.

Install fails partway. Even rarer, but if it happens you’ll see a clear error and the partial install is rolled back. Reach out to support if it’s not obvious.

Updates

Library toolkits update when their maintainer (Jootle for official, the submitter for community) publishes a new version. You’ll see an “update available” indicator on the toolkit; one action applies it.

Custom (your-own) toolkits update when you re-import a newer version of the .jtf.json file.

Uninstalling from the library view

Each installed toolkit has an uninstall option in its detail page. Removing a toolkit is reversible (data is preserved by default); deleting a toolkit’s data is a separate explicit action and is irreversible.

Suggesting a toolkit

If there’s a toolkit you wish existed, tell us. Suggestions are how the library grows — the contact form, the feedback button in the library, or directly via email all work.

If you build a toolkit you’d be willing to share, the community submission flow is in the library’s settings. We review and publish if it fits.