Connecting to Databases

You can connect to, and run queries to fetch and update data directly from the Appsmith editor.

Supported Databases

Appsmith supports the following databases:

General Notes

Each saved database connection is referred to as a Datasource in Appsmith. You can connect to one or more datasources from your app.


Connection management

Appsmith creates a new connection pool with the database server when you first connect the database server to your app. All subsequent queries executed by Appsmith against your database then re-use this connection. This ensures that at run-time your queries are executed fast.

In the event of a server restart/update, all connections to your database server are closed. In this case, Appsmith opens a new connection when your application executes its first query. This connection is then maintained for future use. If the connection has been idle for a long time, your database server may close the connection. Again, in this case, Appsmith will open a new connection on the first query execution.

For certain plugins like PostgreSQL, and MySQL, Appsmith creates and maintains a connection pool because multiple queries cannot be executed against a single connection.

Concurrent queries

Appsmith limits maximum queries that can run concurrently on a database to be 5. If the application attempts to make more queries concurrently, you'll see an error saying Connection not available.


Appsmith safely encrypts all your database credentials and stores them securely. Appsmith also does not store any data returned from your data sources and acts only as a proxy layer to orchestrate the API / Query calls. Since Appsmith is an open-source framework, you can deploy it on-premise, and audit it to ensure none of your data leaves your VPC.

Setting up a Datasource

Steps to set up a datasource

  1. Go to the page in your app that will connect to this datasource


  2. Go to DB Queries on that page.

  3. Click on + next to DB Queries


  4. You’ll see a list of existing Datasources that this page can connect to


  5. Click on **+ New Datasource


  6. Choose a Datasource type from the list of supported types


  7. Provide the required configuration details of your database. You might need to contact your database admin for the connection credentials that are required to configure the database.

  8. Click on Test to verify that Appsmith is able to connect to your database using the details provided by you


  9. Save your datasource


If you are hosting Appsmith, you must whitelist the IP address of the Appsmith deployment. Whitelist to connect to your database from our cloud-hosted version.

A step-by-step guide to doing this on AWS is available here.

Click to expand

Scope of a datasource

Datasources configured within one page of an app can be accessed from:

  • Other pages of the same app

  • Other apps of the same organization

Naming a datasource

Each datasource must be given a name. Since the scope of the datasource is that of its parent organization, the name of a datasource must be unique within its parent organization. Names are case sensitive.

Deleting a datasource

You can delete a datasource only if no queries have been set up on it.

To delete a datasource:

  1. Go to any app that has access to the datasource


  2. Go to any page within the app


  3. Go to DB Queries within that page.

  4. Click on + next to DB Queries


  5. You’ll see a list of Datasources.

  6. Look for the Datasource that you want to delete.

  7. Click on Edit Datasource.

  8. You’ll see a page to edit the datasource’s configuration.

  9. Click on the Delete button at the bottom of the page


Querying a database

You can write queries to fetch from and update data of a datasource using the query editor interface provided by Appsmith for each database type.

Setting up a query

To set up a query:

  1. Go to the page that needs to run this query.

  2. Go to DB Queries → +.

  3. Choose the required datasource type.

  4. Click on New Query.

  5. You will be taken to the query editor to write the query.

  6. Note that the query is created with a default name. It’s recommended that you rename it for readability.

  7. Write your query in the syntax that is valid for your datasource type. For example, if your datasource is a MySQL database, your query needs to be a valid MySQL query.

Using JavaScript in a query

In addition to allowing you to write a valid query for your datasource, Appsmith allows you to write JavaScript in your query. This comes in handy when you want to take an input(s) from a widget. For example, you can use JavaScript in your query to return data of a specific user that is selected in your dropdown widget.

To write JavaScript in the query, enclose your code within the mustache template {{ }}.

Saving a query

Queries are auto-saved. This means that -

  1. As soon as you click on New Query, the query is saved with the default name, even though you haven’t written the query yet.

  2. All changes to the query that you write are auto-saved in real-time. This ensures that you never lose your work.

Though changes to a query are saved in real-time, these changes will be reflected in your live application only after you deploy.

Scope of a query

A query and its results can be accessed from only within widgets of the page that it is part of. That is, its scope is limited to its parent page.

Naming a query

A query must have a name. The name is its unique identifier. It is used to access the query results. In that sense, a query’s name is like a variable’s name in your programming language. You can access the various properties of the query results object using the query’s name.

Since the scope of a query is its parent page, all queries within a page must have unique names. Query names are case-sensitive.

Testing your query

Click on the Run button to see if query execution succeeds. If the query execution succeeds then a success message will pop up on the screen in the top right corner.

Query Settings

You can specify the following settings in the Query Settings tab on the Appsmith Query Editor:

Run query on page load

This allows you to configure whether the query should load on every page load. By default, it is turned off. You can use this setting to tune the performance of your page as per your requirements.

Request confirmation before running query

This enables you to set up a confirmation pop-up modal before a query is run in an application. This setting comes in handy when a query deletes data from a datasource.

Query timeout (in milliseconds)

It’s the time till which Appsmith server waits for the query to execute before closing the connection. By default, it is set to 10000 ms. If your query takes longer than this to return results, Appsmith will throw a timeout error.

Running a query

Manually running a query only helps you test the query. Whereas, when you build an application, you’ll need the app to trigger the query to run when an event. Appsmith allows you to trigger this on a widget’s events, such as onClick of Button widget, onRowSelected for table widget, etc. You can bind an event to run a query in two ways:

  • Using GUI:

    1. Go to the event name in the widget’s property pane

    2. Choose the option Execute DB Query from the dropdown that lists actions

    3. Choose the name of the query that you want to run

  • Using JavaScript

    1. Click on the JS icon next to the event name to enable JavaScript in the specific event of the widget to which you want to bind the query

    2. Type {{ }}

If you are an Appsmith beginner, we recommend that you use GUI instead of JavaScript, so that you can build apps quickly without hurdles. Once you have configured it correctly using the GUI, we recommend that you click on the JS icon next to your event. This will show you the JavaScript equivalent of your configuration. This helps you learn to use JavaScript to configure event behavior from next time onwards!

Accessing query results

A query’s results are stored in an object that is identified by the query’s name. You can access the query’s results in the data property of the object. For example, if the query’s name is sampleQuery, to access its results you’ll write {{ }}.

Query results object

All queries return an array of objects where each object is a row returned by the query and each property in the object is a column. This object is immutable. So, any transformation you run on the query’s results will not change the data the transformation runs on, but only return new data.

Scope of query results

A query’s results can be accessed only from a widget belonging to the same parent page as that of the query, but can’t be accessed from any widget belonging to another page. The results also can’t be accessed from other queries, or APIs belonging to the same parent page as that of the query.