Database Node

Database nodes enable interaction with different databases, allowing for a range of operations including data retrieval, data insertion, updates, and execution of stored procedures. Each type of database node—MongoDB, PostgreSQL, MySQL, Redshift, and MS SQL Server—has unique settings to configure, reflecting the distinct features and capabilities of the respective database systems.

Adding a Database Node

  1. Within the workflow canvas, you would typically click the '+' or 'Add Node' button to reveal the list of nodes and select the type of database node you need—be it MongoDB, PostgreSQL, MySQL, Redshift, etc.

  2. Now, here either you can use the prebuid datasets, or you can create a new one.

      1. Inside this editor modal, you can write queries to customize the action. You can also edit the dataset by clicking on the pen🖊️ icon.

      2. This will redirect you directly to the connectors page where you can configure your connector. And after configuring, come back to this same editor, and here you can click the refresh ↻ button. Then you can see the connector in the dropdown list.

  3. Next, configure the connection settings for your database, including host, port, username, password, and other required details.

  4. After filling in all the connector details click on the Test Connection and check if the connector is working properly or not i.e. credentials are correct for your connectors. And after that publish the connection in staging first by clicking "Publish in Staging" and then repeat the same thing in production. Then finally publish it in production by clicking on Publish in Production button.

Configuring Database Nodes

Once you've added the Database node, you can now configure the database node by following the below steps:

The database node has 3 tabs:

  1. Input Params tab

  2. Test Result

  3. Settings

Input Params Tab

Inside the input params tab, you'll get a couple of options to configure the database nodes.

  1. Action Dropdown: There are two types of query actions that you can perform inside the database node:

    • SELECT Query: You can run the general select query to select one or many attributes of the database. In case you want to just show one or more attributes if the previous nodes are successfully executed, then you can use the SELECT query. This can be done by writing a SQL query for relational databases like PostgreSQL and MySQL, or a BSON query for MongoDB.

    • INSERT or UPDATE Query: You can also insert new values to the database or define the criteria for the records that need to be updated and specify the new values. Again, this will be in the form of a SQL or BSON query, depending on the database. Please read about supported/non-supported queries from respective DB pages.

  2. Integration Dropdown: In this option, you can select the database you intend to interact with from a list of preconfigured database integrations. You can also edit the database connector from the pen🖊️ button just at the right side of the dropdown.

  3. Schema tab: Inside the schema section, you can access all the schema from the database that you're using. It helps you by giving you the database attributes as schema which you can use and create queries based on that.

Test Results Tab

Once you've configured your database, you can click on the "Test" button and then it will be executed and in the "Test Results" tab you'll be able to see the output of the query.

This helps you to observe the results or any errors that may occur, which will help in troubleshooting and validation.

Settings Tab

Adjust additional configurations for how the database node will operate within your workflow.

  • Timeout Setting:

    • Set a duration after which the database operation should time out if not completed.

  • Row Limit Setting:

    • Define the maximum number of rows to be processed during the database operation within the workflow.

  • Cache Option:

    • Determine if the results should be cached, which can improve performance for frequently run queries with unchanged results.

  • Time to Expire Setting:

    • Specify the time after which the cached data expires and can no longer be used in the workflow.

Last updated