Beginner's Guide to ToolJet: Getting Started in 2026

If you’re an AI beginner or a non-developer asking “how do I build internal tools with ToolJet,” here’s the short answer: ToolJet is a free, open-source platform that lets you create admin panels, dashboards, and data-entry apps by dragging and dropping components — no coding required. It’s genuinely beginner-friendly, free to start, and best for simple internal tools that would otherwise require hiring a developer.

How This Guide Was Built

This guide is based on official documentation, pricing pages, and community reports — we did not run the tool hands-on. We drew from the official ToolJet site, the pricing page, the docs (quickstart, Build with AI, user roles), and the GitHub repo, verifying tiers, free-plan limits, signup flow, and first-app steps. Last verified: August 2026.

What ToolJet does and when to use it

ToolJet is an open-source, low-code builder for internal tools — you drag components onto a canvas and connect them to your data. It’s AGPL-3.0 licensed with roughly 40.8k GitHub stars GitHub repo, 80+ pre-built components, and 80+ data source integrations ToolJet site. Use it for admin panels, dashboards, CRMs, and data-entry apps.

The integrations include PostgreSQL, MySQL, MongoDB, Stripe, Slack, Google Sheets, Airtable, Notion, and Salesforce ToolJet site. There’s also a built-in ToolJet Database (Postgres-backed, 5 tables free) ToolJet site, plus “Build with AI” — type a plain-English prompt and ToolJet generates the app for you Build with AI docs.

Use cases for ToolJet include: a customer admin panel to view and edit customer records, an inventory dashboard to track stock levels, an expense tracker for your team, a lightweight CRM to manage leads, and a data-entry app for forms and approvals. Our review rates ToolJet 8.4/10 — see the full breakdown in our ToolJet review.

ToolJet vs alternatives: which should you pick?

Pick ToolJet for a free, open-source start with a built-in database; pick Retool for enterprise features when you’re ready to pay per user; pick Budibase for another open-source option with different hosting tradeoffs. Here’s a side-by-side look at the main options:

Retool and Budibase prices were verified from their official pricing pages at the time of writing — check Retool pricing and Budibase pricing for current numbers. For a deeper breakdown, see our ToolJet review and our internal tool builder comparison.

How do I build internal tools with ToolJet?

Building an internal tool with ToolJet is a six-step process that takes about 30 minutes the first time. You sign up free, create an app, drag components onto a canvas, connect data, make it interactive, and publish. Here are the steps based on the official quickstart guide:

Step 1 — Sign up (free): Go to tooljet.com, click Sign up, enter your email, enter the activation code they email you, then set a workspace name and password. You land on the Free plan ($0 — no credit card; note limits: 2 builders, 50 end users, 2 apps, 100 AI credits/mo, 5 DB tables pricing).

Step 2 — Create your first app: From the dashboard, create an app called “Employee Directory”. You’re now in the visual builder.

Step 3 — Build the UI: Drag a Table component onto the canvas from the 80+ pre-built components. Components are the building blocks of every ToolJet app — tables, forms, buttons, text, charts, and more — and you add them from the component palette on the left, then arrange and resize them on the canvas.

Step 4 — Add data: Create a ToolJet Database table named employees (the built-in Postgres-backed database, 5 tables free). Add a query getEmployees that lists rows and turn ON “Run query on application load”. A query is how ToolJet talks to a data source — it’s a saved request that returns data, and the response panel shows you exactly what came back. Bind the table’s Data property to {{queries.getEmployees.data}} — note the double curly braces, they’re required — so the table renders whatever the query returns.

Step 5 — Make it interactive: Add a second query addEmployees that creates a row. Add event handlers: on “Add new rows” run query addEmployees; on “Query Success” run query getEmployees to refresh the table.

Step 6 — Publish: Preview to check your app, then Release — end users can only see released apps — and Share the link. Never skip Release. Preview shows you the builder view so you can catch mistakes, while Release publishes the app for everyone with the right role; until you hit Release, end users see nothing at all.

Everything above works on the $0 Free plan; self-hosting is also free if you run Docker yourself pricing. The end result: your team opens the shared link, sees the employee list load automatically thanks to “Run query on application load”, adds new rows through the table’s built-in add-rows action, and watches the list refresh on its own when the event handler fires — no page reloads, no code.

Settings beginners should know on day one

There are five settings that will save you hours of confusion if you understand them on day one. The key idea: ToolJet separates building from publishing, and it gives you granular control over how data loads and refreshes. Master these five before you build anything real.

• User roles: There are three roles — Admin (full control), Builder (can create and edit apps), and End-user (can only view released apps) user roles docs. Assign roles carefully so end users don’t accidentally edit your apps.
• Preview vs Release vs Share: Preview shows you the app as a builder; Release makes it live for end users; Share gives you a link to the released app. End users can never see unreleased apps quickstart guide.
• “Run query on application load” toggle: This toggle, found on each query, tells ToolJet to fetch data automatically when the app opens. Without it, your tables stay empty until a user triggers a query manually.
• Event handlers: These let you chain actions — for example, after a “create row” query succeeds, automatically run a “refresh table” query. They’re the glue that makes your app feel responsive.
• AI credits meter: The Free plan includes 100 AI credits per month; if you use “Build with AI” heavily, you can buy add-ons at $1 per 100 credits pricing. Keep an eye on the meter so you don’t run out mid-build — it’s the one free-plan limit beginners actually hit in a busy month.
• Workspace constants: These are shared values (like a company name or a default date) that you define once and reference across all your apps — much easier than updating the same value in ten places. Change the constant in one spot and every app that references it picks up the new value automatically.

3 pro tips beginners discover late

These three tips come up again and again in community discussions about ToolJet. They’re not in the quickstart guide, but they save beginners real time, and each one is grounded in how the platform actually works. Learn them early and your first few apps will go much more smoothly.

1. Put secrets in environment variables or workspace constants. Never hardcode API keys, passwords, or tokens directly in your queries. If you do, they’re visible to anyone who can view the app’s source. Store them in environment variables (for self-hosted) or workspace constants, and reference them by name. The difference matters: environment variables live on the server, while workspace constants live inside your ToolJet workspace — either way, the value stays out of the app’s source code. This also makes it trivial to rotate credentials later.

2. Test your data source connection before building UI on top of it. It’s tempting to drag components first and connect data later — but if the connection fails, you’ll have a beautiful empty app and no idea why. Create a query, run it, and confirm you see data in the response panel before you build the UI. This one habit will save you an hour of debugging.

3. Write specific “Build with AI” prompts. The “Build with AI” feature generates an app from a plain-English description Build with AI docs. A generic prompt like “make me a dashboard” yields a generic app. Instead, describe the exact data, the screens you need, and the actions users should take — for example, “a customer admin panel with a table of customer names, emails, and status, plus a form to add new customers.” Specific prompts produce dramatically better results.

Common mistakes (and how to avoid them)

There are five mistakes that trip up nearly every ToolJet beginner, and they’re all easy to fix once you know what to look for. Most of them come down to forgetting how ToolJet separates editing from publishing — or skipping basic data checks before building the UI.

• Never pressing Release — end users can’t see unreleased apps; hit Release after Preview. Preview and Release feel similar in the builder, but only Release makes the app visible to end users.
• Hardcoding API keys — use environment variables or workspace constants instead of embedding secrets in queries.
• Not testing the data source connection — verify it before building, or you’ll debug a blank app later.
• Forgetting “Run query on application load” — tables stay empty until a query runs; turn this toggle on for your initial data query.
• Missing double braces in bindings — it’s {{queries.getEmployees.data}}, not single braces; single braces won’t render data.

Also watch the free-plan limits (2 apps, 2 builders, 5 tables, 100 AI credits) so you’re not surprised mid-build pricing.

FAQ

Here are answers to the three questions beginners ask most often about ToolJet: whether it’s free, whether you need to code, and what the AI builder does. Each answer is drawn from official ToolJet sources and verified against the pricing page, so you can trust it before signing up.

Is ToolJet free?

Yes: Cloud Free is $0 with 2 builders, 50 end users, 2 apps, 100 AI credits/mo and 5 DB tables; self-hosting is also free if you run it yourself pricing. Paid plans start at $79/builder/mo for more apps, users, and AI credits.

Do I need to know how to code to use ToolJet?

No: drag-and-drop builder plus 80+ pre-built components; “Build with AI” generates an app from a plain-English prompt ToolJet site. You can build functional internal tools without writing a single line of code.

What is “Build with AI” in ToolJet?

A feature where you type a plain-English description and ToolJet generates the app for you; specific prompts produce better apps, and it consumes AI credits (100/mo free) Build with AI docs. It’s a fast way to scaffold a first version.

Where to go next

You now know the basics of building internal tools with ToolJet — sign up free, create an app, connect data, and publish. The next step is to go deeper into specific features and compare ToolJet against other options; the links below show it side by side with Retool and Budibase.

• Our ToolJet review — a full 8.4/10 breakdown of strengths, weaknesses, and who should use it.
• The internal tool builder comparison — see how ToolJet stacks up against Retool, Budibase, and others.
• Our content pipeline explainer — how we research and verify the tools we cover, so you know what to trust.