Enable Postgres in Kizen
Audience: Admins, Developers, Solution Architects
Purpose: Explains how to configure the Postgres integration to use live PostgreSQL data in Agentic Workflows
Overview
Caution: This setup reflects Kizen's default configuration. Your administrator may have customized your layout, so columns or navigation may appear differently. Trial accounts may have limited features.
To use PostgreSQL data in Agentic Workflows, you must first enable the Postgres integration in Kizen.
Before You Begin
Before you enable the Postgres integration, ensure you have:
Any PostgreSQL instance, whether self-hosted or managed through Amazon RDS, Google Cloud SQL, Aurora PostgreSQL, or a similar service
A PostgreSQL database, version 11 or later, that is network-reachable from Kizen's egress IP addresses
A PostgreSQL role with the necessary read or write privileges on the target database tables
Org Admin access in Kizen
Enable Postgres in Kizen
To enable Postgres in Kizen:
Configure your PostgreSQL network
To configure your PostgreSQL network to work with Kizen:
Add Kizen's egress IP addresses to the allowlist on your PostgreSQL database or proxy. For the current list of egress IPs, contact your Kizen representative.
Set your firewall to allow inbound TCP traffic on the PostgreSQL port. This port is usually but not necessarily
5432. If you aren't sure of the correct port number, check your PostgreSQL configuration.Optionally turn on SSL for your PostgreSQL instance. To maintain security, we recommend that you use SSL unless you connect to the instance through a trusted private network or VPN.
Turn on the Postgres connection
Find the Postgres Connection card, and turn on the slider.

Note: If the Update Integration Secret modal appears after you turn on the slider, skip ahead to Step 6.
Enter your PostgreSQL credentials
In the Integration Secret field of the modal, enter your PostgreSQL connection credentials as a JSON object. The JSON object must contain host, port, user-name, and password keys, like this:
Store multiple environments as nested JSON objects:
For descriptions of the keys, see the following table:
host
String
The host name or IP address of the PostgreSQL server
port
Integer
The PostgreSQL server port
user_name
String
The user name of the connecting PostgreSQL account
password
String
The password of the connecting PostgreSQL account
Note: Kizen hides your secret once you submit it, so you can't append a new environment to an existing secret. You must re-enter the credentials for all your environments along with the new one. Consider keeping a secure record of each environment's connection details outside of Kizen so you can refer to the full set whenever you add a new environment.
What's Next
Now that you've set up the Postgres integration, you're ready to use the Read Data and Write Data actions in Agentic Workflows. Continue to Add Postgres Data to an Agentic Workflow to learn how.
Postgres, PostgreSQL, and the Slonik Logo are trademarks or registered trademarks of the PostgreSQL Community Association of Canada. Kizen's PostgreSQL integration is not affiliated with, sponsored by, or endorsed by the PostgreSQL Community Association of Canada, the PostgreSQL Global Development Group, or the PostgreSQL Project.
Last updated
Was this helpful?



