Integrating Tooljet with Databases and REST API: A Complete Guide

When building an internal tool on Tooljet, a typical picture: the database does not respond due to a firewall, the REST API returns raw data with nested objects, and security tokens lie in plain view in configs. Each of these problems can stall development for days. We have been through dozens of such projects and have developed an approach that guarantees stable connectivity and security.

In this guide, we will walk through how to configure Tooljet to work with databases (PostgreSQL, MySQL, MongoDB), REST APIs, and SaaS services while avoiding common mistakes. Tooljet cuts internal tool development time by 5x compared to a custom React UI, but only if the data sources are correctly configured. Incorrect connections lead to duplicate queries, data leaks, and wasted time.

What problems do we solve?

• N+1 queries — when each widget makes a separate database query. We optimize by combining queries and caching.
• Token security — sensitive data (API keys, passwords) often ends up in the query configuration. We adopt Constants and environment variables.
• Complex transformations — API responses contain extra fields, amounts in cents, dates in wrong formats. We use JavaScript Transformations.
• Connection errors — incorrect host, port, or SSL certificates. We test every connection via the Test Connection button and fix issues.

How we do it

We start with an audit of the sources: compile a list of all databases, APIs, and SaaS services that need to be integrated. Then we configure connections, create the first queries and transformations. One recent project — connecting PostgreSQL with 15 tables and a billing system’s REST API. Below are example configurations.

PostgreSQL setup example

Name: Production DB
Host: db.example.com
Port: 5432
Database: app_db
Username: tooljet_ro
Password: ****

The Test Connection button helps catch errors before saving. After a successful test, we add queries like SELECT * FROM orders WHERE status = 'pending' and pass parameters from UI components.

REST API example (GET and POST requests)

{
  "path": "/users/{{components.userIdInput.value}}",
  "method": "GET",
  "headers": {
    "X-Trace-Id": "{{utils.uuid()}}"
  }
}

{
  "path": "/orders/{{components.ordersTable.selectedRow.id}}/refund",
  "method": "POST",
  "body": {
    "amount": "{{components.refundInput.value}}",
    "reason": "{{components.refundReason.value}}",
    "operator": "{{currentUser.email}}"
  }
}

Constants — sensitive values (tokens, keys) are stored in Tooljet Constants, not in the query configuration.

Transformations

const raw = data.orders;
return {
  items: raw.map(o => ({
    id: o.id,
    date: new Date(o.created_at).toLocaleDateString('ru-RU'),
    amount: `${(o.total / 100).toFixed(2)} ₽`,
    status: o.status
  })),
  total: raw.length,
  sum: raw.reduce((s, o) => s + o.total, 0) / 100
};

Event Handling

// Run on query success
await queries.getUsersList.run();
components.statusMessage.setText('Successfully updated');
setTimeout(() => components.statusMessage.setText(''), 3000);

Why trust professionals with the setup?

We guarantee connection stability, data security, and post-deployment support. Our engineers hold Tooljet certifications and have experience with cloud infrastructures (AWS, Vercel, Docker). You receive:

• Documentation for every source.
• Training for your team on Tooljet.
• Technical support for 2 weeks after launch.

Process

1. Analysis — we study your data sources, network constraints, and security requirements.
2. Design — define query structure, transformations, and Constants configuration.
3. Implementation — set up connections, write queries and transformations, test each connection.
4. Testing — verify all scenarios: empty responses, errors, high loads.
5. Deploy — roll out the solution in your environment, deliver documentation, and conduct training.

What's included

Timeline and cost

• Basic setup (3–5 sources) — 1–2 days.
• Extended integration (up to 10 sources + custom transformations) — 3–5 days.
• Comprehensive solution (with training and support) — up to 7 days.

Save up to 40% of your developers' time — Tooljet takes over the routine.

Typical connection errors

Connection issues often arise from common mistakes. Connection refused is usually due to incorrect host or port, or a firewall block. SSL handshake failed appears with certificate problems — temporarily you can disable SSL, but for production it's better to add the correct certificate. Timeout occurs on too long queries or a slow database; the solution is to increase the timeout or optimize indexes. 401 Unauthorized — the token is expired or invalid; update it in Constants. Incorrect data in response — an error in the transformation; debug JavaScript in the Tooljet console.

Comparison with custom solutions

Order your Tooljet setup today and save up to 40% of your team's time. Leave a request for a consultation — we'll contact you within an hour.

Backend Development Services: Laravel, Node.js, Go, Django, PostgreSQL

On a production server at 3:14 AM, the Laravel Jobs queue stopped processing. 40,000 unprocessed jobs in Redis. Cause: worker crashed due to a memory leak in one of the Jobs (leak via a static variable in an Eloquent observer), supervisor didn't restart it because of misconfigured stopwaitsecs. This is not a hypothetical scenario — it's Tuesday. We analyzed such an incident on a project with 500 RPS load: diagnosis took 4 hours, fix — 20 minutes. So you don't lose money on downtime, we offer backend development services with a focus on production-grade reliability. We'll assess your project in 2 days.

Backend is what works when no one is watching. Or doesn't work. We guarantee you'll have the first option.

How do we ensure production-grade reliability from day one?

What we do correctly from day one

Service Layer over Fat Controllers. Controller receives HTTP request, validates it via Form Request, passes data to Service, returns response. Business logic in Service, not Controller. This sounds trivial, but most legacy projects have controllers with 500 lines and SQL queries inside.

Repository Pattern we use cautiously. If you just wrap Model::where(...) in a repository method — that's boilerplate without benefit. Repository is justified when: you need to abstract from the data source (DB + cache + external API) or when query logic is complex enough to isolate.

Jobs, Events, Listeners. Everything that can be async — make async. Sending email, PDF generation, external API sync, aggregate recalculation — into Queue. Laravel Horizon for queue monitoring in Redis: see throughput, failed jobs, processing time per queue.

How Octane handles high load

Laravel Octane with RoadRunner or Swoole keeps the app in memory between requests — removes bootstrap overhead (config loading, class autoloading) on each HTTP request. Gain: 3–8x on synthetic benchmarks, 2–4x on real applications. Important: no state between requests in static variables — that leads to exactly the incidents from the beginning. We use this in projects with >1000 RPS.

What to do about N+1 queries

N+1 is the most common cause of slow pages in Laravel apps. Standard story: page worked fine on dev with 10 records, on production with 10,000 — 8-second load.

Laravel Debugbar in dev environment shows the number of queries per page. More than 20 queries per page — signal for audit.

Model::preventLazyLoading(! app()->isProduction());

Telescope for profiling in staging: logs all queries, jobs, mail, notifications with time detail. Numbers: after implementing eager loading, page load time drops from 8s to 0.3s — 27 times faster.

PostgreSQL: indexes that are actually needed

PostgreSQL 14+ is the primary DB on all projects. We use PgBouncer + PostgreSQL combination. 10+ years experience, more than 50 backend projects, 5 years on the market.

How PostgreSQL helps avoid slow queries

Composite indexes for frequent WHERE + ORDER BY. If you have WHERE user_id = ? AND status = ? ORDER BY created_at DESC — you need (user_id, status, created_at DESC). A separate index on (user_id) doesn't help much with sorting.

Partial indexes. If 95% of queries go with WHERE status = 'active':

CREATE INDEX idx_orders_active ON orders (created_at DESC)
WHERE status = 'active';

The index is small, fast, covers the main load.

GIN indexes for JSONB and arrays. @> operator without GIN index — seq scan. With index — fast even on millions of rows.

GIN for full-text search. to_tsvector + GIN instead of LIKE '%query%'. LIKE without index is always seq scan. With pg_trgm extension and gin_trgm_ops — supports LIKE with index, useful for CRM search by partial match.

Connection pooling: why it's more important than it seems

Rails, Laravel, Django open a new connection to PostgreSQL for each PHP/Python process. With 100 workers — 100 connections. PostgreSQL starts degrading from 200–300 active connections — overhead on connection management becomes significant.

PgBouncer — connection pooler in front of PostgreSQL. Transaction pooling mode: connection to PostgreSQL is occupied only during a transaction, returned to pool between requests. 1000 application workers → 20–50 actual connections to PostgreSQL. This reduces latency by 40% and hosting costs by 30%.

Node.js with Fastify: when it's better than Laravel

Node.js is justified for:

• Realtime: WebSocket servers, Server-Sent Events, chat, live updates
• Streaming: large files, video, streaming data
• High I/O concurrency: many parallel requests to external APIs without heavy business logic
• Serverless: Lambda/Cloud Functions — Node.js starts faster than PHP

Fastify over Express: 2–3 times faster on benchmarks, built-in JSON Schema validation, better TypeScript support, plugin architecture.

Typical realtime architecture: Laravel — core business logic and REST API. Node.js + Socket.io or ws — WebSocket server. Laravel publishes events to Redis Pub/Sub, Node.js subscribes and broadcasts to clients. This separation allows scaling the WebSocket server independently of the main app.

Go: microservices and high load

Go we use for:

• High-load microservices (>10,000 RPS)
• Background workers with strict latency requirements
• DevOps tools and CLI
• gRPC services in microservice architecture

Goroutines — thousands of times cheaper than OS threads. 10,000 concurrent connections on Go is normal on one server.

But Go is not a silver bullet. Development is slower than Laravel: more boilerplate, no ORM at Eloquent level, error handling with if err != nil everywhere. Justified only when performance is a real requirement, not an assumption.

Django and Python backend

Django with DRF (Django REST Framework) — for tasks where Python is needed: ML pipelines, data processing, integrations with AI tools.

Celery for background tasks — similar to Laravel Queue but more complex to configure. Celery Beat for cron tasks.

Django ORM vs raw SQL: ORM is convenient for CRUD. For analytical queries with multiple JOINs, window functions, and CTEs — connection.execute() with raw SQL is more readable and predictable.

Redis: not just cache

Redis in our projects plays multiple roles:

Redis Cluster for horizontal scaling. Sentinel for automatic failover on standalone setups.

Deployment and infrastructure

Docker + docker-compose — standard for local development and production. Each service in a container: PHP-FPM/Octane, Nginx, PostgreSQL, Redis, Queue Worker, Scheduler.

CI/CD via GitHub Actions:

1. Run tests (PHPUnit / Pest, Vitest, Playwright)
2. Build Docker image
3. Push to Container Registry
4. Deploy: docker pull → docker-compose up -d on server, or Kubernetes rolling update

Zero-downtime deploy for Laravel: php artisan down --secret=TOKEN is not needed with proper configuration. Strategy: new container starts next to the old one, Nginx switches traffic after health check, old container stops.

Monitoring: Sentry for exception tracking with alerting in Slack/Telegram. Grafana + Prometheus (or Grafana Cloud) for metrics: CPU, memory, request rate, queue depth, database connection count. Alerts on: error rate > 1%, p99 latency > 2s, queue depth > 1000 jobs.

What's included in turnkey work

• Architecture design (API documentation, DB schema, service diagram)
• Implementation according to agreed specification with code review
• CI/CD, monitoring, alerting setup
• Load testing (k6, wrk) with report
• Handover of source code, access, deployment instructions
• Training of customer's team (2-3 sessions)
• Warranty support for 1 month after delivery

Timeline benchmarks

Pricing is calculated individually after analyzing load, integrations, and business logic. Contact us for a free audit of your current backend — get an optimization plan in 2 days. Request a consultation.