MySQL is a supported SQL destination in the current app and is useful when downstream tools or applications already expect MySQL tables.Documentation Index
Fetch the complete documentation index at: https://docs.mantrixflow.com/llms.txt
Use this file to discover all available pages before exploring further.
Current connection form
The current MySQL destination form asks for:-
Connection Name -
Host -
Port -
Database -
Username -
Password -
SSL Mode -
Portdefaults to3306. -
SSL Modeoptions are available in the connection form. -
Use the builder to set the final destination
SchemaandTable.
Good first use cases
- operational reporting tables
- internal tool read models
- application-facing SQL tables fed by a pipeline
Before you connect
- Create a dedicated write user for the target MySQL database.
- Decide which schema and table name you want to use in the destination panel.
- Validate one destination table manually before broadening the rollout.
Step by step
- Open Connections and click + New Connection.
- Set the role to Destination and choose MySQL.
- Fill the form with real values, for example:
Connection Name:MySQL ReportingHost:reporting.cluster-abcdefghijkl.us-east-1.rds.amazonaws.comPort:3306Database:reportingUsername:mf_writerSSL Mode:require
- Click Test Connection and save the connection after the test succeeds.
- In the builder’s Destination panel, configure:
Connection:MySQL ReportingSchema:analyticsTable:orders_liveWrite mode:Upsert
- Save the pipeline and run one manual sync before enabling a schedule.
Real-world example
A support operations team lands GitHub and HubSpot data into MySQL so an internal application can query recent issues, pull requests, and CRM records from one operational store.Troubleshooting
- If the test fails, confirm the database host, SSL mode, and write user credentials.
- If destination validation fails, make sure the target schema and table names are correct for the environment.
- Keep the first rollout on
Upsertand validate the rows with SQL before adding a schedule.