For the complete documentation index, see llms.txt. This page is also available as Markdown.
Add Postgres Data to an Agentic Workflow
Audience: Admins, Developers, Solution Architects
Purpose: Explains how to read and write PostgreSQL data from an Agentic Workflow to query or update your external PostgreSQL database
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.
Once you set up the Postgres integration in Kizen, you can read and write PostgreSQL data directly from Agentic Workflows with the Read Data and Write Data actions.
Before You Begin
To add Postgres data to an Agentic Workflow, you need:
A PostgreSQL user role with the necessary read or write privileges on the target database tables.
Add Postgres data to an Agentic Workflow
To add Postgres data to an Agentic Workflow:
1
Go to the Agentic Workflow builder
In the global navigation, select Agentic Workflows. Then, to open the builder, do one of the following:
Select New Agentic Workflow.
Select the name of an existing Agentic Workflow.
2
Add an action to the workflow
Select +, and then select Add Action.
3
Select the Postgres Connection action
In the Add Action modal that appears, scroll to the Integration section, and select the Postgres Connection card.
4
Choose whether to read or write PostgreSQL data
In the Action Settings section of the Add Action modal, select the Action dropdown menu, and do one of the following:
To read PostgreSQL data, select Read Data.
To write PostgreSQL data, select Write Data.
Caution: The Write Data action can insert, update, or delete records in your external PostgreSQL database. Validate your query against a non-production database before running it against production data.
5
Configure the sources for the script inputs
For each of the fields in the Script Inputs section of the modal, select the source of the field's value from the Input Source dropdown menu, and then configure the source with the additional controls that appear.
Note: The order of the fields on the screen depends on whether you selected the Read Data or Write Data action.
The fields are as follows:
Field
Type
Description
Required?
Query
String
The SELECT statement to execute.
Yes
Database
String
The name of the target PostgreSQL database.
Yes
Connection Secret Tag
String
The name of the PostgreSQL environment from your integration secret to execute the query on. Configure this source when you have more than one environment in your secret.
Not in a single-environment configuration
Return Single Value
Boolean
Whether you expect to return a single value (true) or multiple values (false).
Yes
Note: Always use the LIMIT clause in SELECT queries against large tables. Results sets larger than 5 MB might be truncated or cause memory issues.
6
Configure the destinations for the script outputs
For each of the fields in the Script Outputs section of the modal, select the destination of the field's value from the Output Destination dropdown menu, and then configure the destination with the additional controls that appear.
Note: The Read Data action uses only the Result field as a script output. The Write Data action uses both Result and Result Status.
The fields are as follows:
Field
Type
Action
Description
Required?
Result
String
Read Data
The result of the query
Yes
Result Status
String
Read Data, Write Data
The status of the write operation
Yes
7
Configure error handling
In the Error Handling section of the modal, specify how to handle errors in this step of the Agentic Workflow.
8
Save the Postgres Connection action
Select Save.
What's Next
Your Agentic Workflow can now read from or write to your PostgreSQL database. For details on how to fix common technical issues, continue to Troubleshoot Postgres.
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.
