Add MySQL Data to an Agentic Workflow
Last updated
Was this helpful?
Audience: Admins, Developers, Solution Architects
Purpose: Explains how to read and write MySQL data from an Agentic Workflow to query or update your external MySQL database
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 MySQL integration in Kizen, you can read and write MySQL data directly from Agentic Workflows with the Read Data and Write Data actions.
To add MySQL data to an Agentic Workflow, you need:
A MySQL connection to Kizen. See Enable MySQL in Kizen for details.
A MySQL user account with the necessary read or write privileges on the target database tables.
To add MySQL data to an Agentic Workflow:
In the Action Settings section of the Add Action modal, select the Action dropdown menu, and do one of the following:
To read MySQL data, select Read Data.
To write MySQL data, select Write Data.

Caution: The Write Data action can insert, update, or delete records in your external MySQL database. Validate your query against a non-production database before running it against production data.
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:
Database
String
The name of the target MySQL database.
Yes
Return Single Value
Boolean
Whether you expect to return a single value (true) or multiple values (false).
Yes
Query
String
The SELECT statement to execute.
Yes
Connection Secret Tag
String
The name of the MySQL 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
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.
The result of the query comes back as a string. Find the Result field in the Script Outputs section of the modal, open its Output Destination dropdown menu, select where to store the result string, and then configure the destination with the additional controls that appear.

Your Agentic Workflow can now read from or write to your MySQL database. For details on how to fix common technical issues, continue to Troubleshoot MySQL.
Oracle, Java, MySQL, and NetSuite are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Last updated
Was this helpful?
Was this helpful?