Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

MySQL

The world's most popular open-source database

CategoryDeveloper Tools
Authenticationcustom
Version0.2.7
Published scopes0 published scopes
Last updatedSeptember 30, 2026

Overview

Connect MySQL with Flows360

The world's most popular open-source database

Use the MySQL connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 6 actions and no declared triggers.

Available actions

  • Find Rows
  • Insert Row
  • Update Row
  • Delete Row
  • Get Tables
  • Execute Query

Available triggers

  • No triggers are declared in this pinned package.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: MySQL
  • Package: @activepieces/piece-mysql@0.2.7
  • Exact artifact digest: sha256:0ac85d35ec52d35866e7e6405b8abb69fae6808c35ba9b41d95138e2eb13430e
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Find Rows (find_rows), Reads rows from a table Classification: read.
  • Insert Row (insert_row), Inserts a new row into a table Classification: read.
  • Update Row (update_row), Updates one or more rows in a table Classification: read.
  • Delete Row (delete_row), Deletes one or more rows from a table Classification: read.
  • Get Tables (get_tables), Returns a list of tables in the database Classification: read.
  • Execute Query (execute_query), Executes a query on the mysql database and returns the results Classification: read.

Trigger contracts

  • No trigger delivery contracts are declared.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

Authenticationcustom
Supported objects6
Supported actions6
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Host Required
  • Port Required
  • Username Required
  • Password Required · protected credential
  • Database Optional

Supported objects

ObjectReadWriteNotes
Find Rows Yes No Reads rows from a table
Insert Row Yes No Inserts a new row into a table
Update Row Yes No Updates one or more rows in a table
Delete Row Yes No Deletes one or more rows from a table
Get Tables Yes No Returns a list of tables in the database
Execute Query Yes No Executes a query on the mysql database and returns the results

Supported actions

Find Rows · Read

Reads rows from a table

find_rows · Risk: low · Retry: safe

Inputs

  • markdown · string · Optional, n **DO NOT** use dynamic input directly in the query string or column names.n nn Use **?** in the query and dynamic values in args/values for parameterized queries to prevent **SQL injection**.
  • timezone · string · Optional, Timezone for the MySQL server to use
  • table · string · Required
  • condition · string · Required, SQL condition, can also include logic operators, etc.
  • args · array · Optional, Arguments can be used using ? in the condition
  • columns · array · Optional, Specify the columns you want to select
Insert Row · Read

Inserts a new row into a table

insert_row · Risk: low · Retry: safe

Inputs

  • timezone · string · Optional, Timezone for the MySQL server to use
  • table · string · Required
  • values · object · Required
Update Row · Read

Updates one or more rows in a table

update_row · Risk: low · Retry: safe

Inputs

  • timezone · string · Optional, Timezone for the MySQL server to use
  • table · string · Required
  • values · object · Required
  • search_column · string · Required
  • search_value · string · Required
Delete Row · Read

Deletes one or more rows from a table

delete_row · Risk: low · Retry: safe

Inputs

  • markdown · string · Optional, n **DO NOT** use dynamic input directly in the query string or column names.n nn Use **?** in the query and dynamic values in args/values for parameterized queries to prevent **SQL injection**.
  • timezone · string · Optional, Timezone for the MySQL server to use
  • table · string · Required
  • search_column · string · Required
  • search_value · string · Required
Get Tables · Read

Returns a list of tables in the database

get_tables · Risk: low · Retry: safe

Execute Query · Read

Executes a query on the mysql database and returns the results

execute_query · Risk: low · Retry: safe

Inputs

  • markdown · string · Optional, n **DO NOT** use dynamic input directly in the query string or column names.n nn Use **?** in the query and dynamic values in args/values for parameterized queries to prevent **SQL injection**.
  • timezone · string · Optional, Timezone for the MySQL server to use
  • query · string · Required, The query string to execute, use ? for arguments to avoid SQL injection.
  • args · array · Optional, Arguments to use in the query, if any. Should be in the same order as the ? in the query string..

Setup

Setup

  1. Add the MySQL connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • Host (host), required.
  • Port (port), required.
  • Username (user), required.
  • Password (password), required; stored as a sensitive connection value.
  • Database (database), optional.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-mysql@0.2.7; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 6 actions and 0 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Runtime execution evidence is managed separately from package metadata.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required MySQL connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-mysql@0.2.7 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com