MySQL integration

Databases · 9 actions · Custom auth

MySQL database integration for executing SQL queries, managing tables, and performing CRUD operations. Uses the aiomysql driver.

Put MySQL to work View MySQL integration docs

Overview

The ModuleX MySQL integration lets a ModuleX agent operate MySQL on your behalf — running create, update and remove actions across raw queries, rows and query with conditions — directly from a plain-English request, using your organization's own MySQL credentials. No pre-built workflow is required: the agent picks the right MySQL action for the task.

MySQL is a databases platform. ModuleX adds the agent layer: ask for an outcome and it selects and runs the right MySQL action — or, when you want a repeatable process, the composer assembles a MySQL workflow for you, streaming the nodes onto the canvas as it builds.

Ask the assistant

Drive MySQL in plain English

Type what you want. A ModuleX agent picks the right MySQL action — or chains several — and runs it. No workflow to build.

INSERT a new row (returns affected_rows + last_insert_id)
resolves tocreate_row
Find the row I describe and remove it
resolves tofind_rowdelete_row
UPDATE rows matching a WHERE condition
resolves toupdate_row
Show me the tables that match what I describe
resolves tolist_tables

Use cases

What you can automate with MySQL

Find the right row and remove it in one promptfind_rowdelete_row
Run a raw query from a plain-English requestexecute_raw_query
Pull a list of tables for a reportlist_tables

At a glance

MySQL integration at a glance

VendorMySQL

CategoryDatabases

Actions available9

AuthenticationCustom

Uses your own credentialsYes

Works with the assistantYes

Works in the composerYes

Multi-step / tool-chainingYes

Technical referenceView docs

Integration version1.0.0

Last updatedJun 2026

Reference

All 9 MySQL actions

Raw Queries1

execute_raw_query

Execute any SQL statement. Use '%s' for parameterized queries (DB-API style).

Rows4

create_row

INSERT a new row (returns affected_rows + last_insert_id)

delete_row

DELETE rows matching a WHERE condition

update_row

UPDATE rows matching a WHERE condition

find_row

SELECT * FROM table WHERE column <op> value

Query with Conditions1

execute_query_with_condition

SELECT * FROM table WHERE <condition>

Stored Procedures1

execute_stored_procedure

CALL <stored_procedure>(...) with optional parameters

Tables2

list_tables

List all tables and views in the current database

describe_table

Return column metadata for a table (SHOW COLUMNS)

See full parameters and response schemas in the MySQL integration docs

Two ways

Two ways to use MySQL in ModuleX

Ask the assistantType what you want done and a ModuleX agent picks the right MySQL action and runs it — no workflow to build.

Compose a workflowNeed it to happen every time? Describe the process and the composer wires MySQL into a repeatable workflow you can run on a schedule, from chat, or as an API.

Security

Connecting MySQL

CustomMySQL uses a custom authentication flow. ModuleX encrypts whatever credentials you supply and scopes them to your organization.

Step-by-step setup in the MySQL docs

Pairs well with MySQL

Agents often chain MySQL with these — connect them once and the agent can use all of them in a single task.

PostgreSQL10 actions

Snowflake9 actions

Supabase8 actions

Microsoft SQL Server4 actions

FAQ

MySQL + ModuleX FAQ

A ModuleX agent can run any of MySQL's 9 actions — across raw queries, rows, query with conditions and stored procedures — from a plain-English request, using your organization's own MySQL credentials.

No. The agent selects the right MySQL action from your prompt. A workflow is only needed when you want a repeatable process — and the composer builds that for you from a description.

Through a secure MySQL connection; your credentials are stored encrypted and scoped to your organization.

9, spanning raw queries, rows, query with conditions and stored procedures.

MySQL runs on your own credentials, so any MySQL usage is billed by MySQL directly. ModuleX meters the agent run — and if you connect your own model keys, there's no ModuleX markup on model usage.

Put MySQL to work in ModuleX.

Connect MySQL once with your own credentials and let your agent run all 9 actions on demand.

Put MySQL to work View technical docs

Last updated: Jun 2026Browse all 175 integrations →