How to connect 123FormBuilder and MySQL
Create a New Scenario to Connect 123FormBuilder and MySQL
In the workspace, click the “Create New Scenario” button.

Add the First Step
Add the first node – a trigger that will initiate the scenario when it receives the required event. Triggers can be scheduled, called by a 123FormBuilder, triggered by another scenario, or executed manually (for testing purposes). In most cases, 123FormBuilder or MySQL will be your first step. To do this, click "Choose an app," find 123FormBuilder or MySQL, and select the appropriate trigger to start the scenario.

Add the 123FormBuilder Node
Select the 123FormBuilder node from the app selection panel on the right.

123FormBuilder
Configure the 123FormBuilder
Click on the 123FormBuilder node to configure it. You can modify the 123FormBuilder URL and choose between DEV and PROD versions. You can also copy it for use in further automations.
Add the MySQL Node
Next, click the plus (+) icon on the 123FormBuilder node, select MySQL from the list of available apps, and choose the action you need from the list of nodes within MySQL.

123FormBuilder
⚙

MySQL

Authenticate MySQL
Now, click the MySQL node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your MySQL settings. Authentication allows you to use MySQL through Latenode.
Configure the 123FormBuilder and MySQL Nodes
Next, configure the nodes by filling in the required parameters according to your logic. Fields marked with a red asterisk (*) are mandatory.
Set Up the 123FormBuilder and MySQL Integration
Use various Latenode nodes to transform data and enhance your integration:
- Branching: Create multiple branches within the scenario to handle complex logic.
- Merging: Combine different node branches into one, passing data through it.
- Plug n Play Nodes: Use nodes that don’t require account credentials.
- Ask AI: Use the GPT-powered option to add AI capabilities to any node.
- Wait: Set waiting times, either for intervals or until specific dates.
- Sub-scenarios (Nodules): Create sub-scenarios that are encapsulated in a single node.
- Iteration: Process arrays of data when needed.
- Code: Write custom code or ask our AI assistant to do it for you.

JavaScript
⚙
AI Anthropic Claude 3
⚙

MySQL
Trigger on Webhook
⚙
123FormBuilder
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring 123FormBuilder, MySQL, and any additional nodes, don’t forget to save the scenario and click "Deploy." Activating the scenario ensures it will run automatically whenever the trigger node receives input or a condition is met. By default, all newly created scenarios are deactivated.
Test the Scenario
Run the scenario by clicking “Run once” and triggering an event to check if the 123FormBuilder and MySQL integration works as expected. Depending on your setup, data should flow between 123FormBuilder and MySQL (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect 123FormBuilder and MySQL
123FormBuilder + MySQL + Slack: When a new submission is made in 123FormBuilder, the submission data is inserted as a new row in a MySQL database, and a message is sent to a Slack channel to notify the team of the new submission.
123FormBuilder + MySQL + Google Sheets: When a new submission is made in 123FormBuilder, the data is stored in a MySQL database, and the data from the new row in the database is then added as a new row in Google Sheets for analysis.
123FormBuilder and MySQL integration alternatives
About 123FormBuilder
Streamline data collection by connecting 123FormBuilder to Latenode. Automatically trigger workflows when forms are submitted. Route form data to CRMs, databases, or email marketing tools. Use Latenode to validate entries, calculate scores, and manage follow-ups — automating processes with a no-code, scalable workflow.
Related categories

About MySQL
Use MySQL in Latenode to automate database tasks. Read, update, or create records based on triggers from other apps. Streamline data entry, reporting, or inventory management. Latenode's visual editor simplifies MySQL integrations, allowing you to build scalable workflows with no-code tools or custom JavaScript logic.
Similar apps
Related categories
See how Latenode works
FAQ 123FormBuilder and MySQL
How can I connect my 123FormBuilder account to MySQL using Latenode?
To connect your 123FormBuilder account to MySQL on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select 123FormBuilder and click on "Connect".
- Authenticate your 123FormBuilder and MySQL accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I store form submissions directly into my database?
Yes, you can! Latenode allows direct transfer of 123FormBuilder submissions to MySQL, offering a streamlined process. Benefit from secure, centralized data management and in-depth reporting.
What types of tasks can I perform by integrating 123FormBuilder with MySQL?
Integrating 123FormBuilder with MySQL allows you to perform various tasks, including:
- Automatically backing up form data to a secure MySQL database.
- Creating custom reports based on form submission data.
- Updating customer records in your MySQL database upon form submission.
- Triggering personalized email sequences based on form answers.
- Storing survey responses in a structured MySQL table for analysis.
Howsecureisdata transferbetween123FormBuilderandMySQLonLatenode?
Latenode employs secure protocols for data transfer, ensuring your data is encrypted and protected during the 123FormBuilder to MySQL integration.
Are there any limitations to the 123FormBuilder and MySQL integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Large data transfers may experience rate limits imposed by the 123FormBuilder API.
- Complex MySQL database schemas may require custom JavaScript for optimal integration.
- Real-time synchronization depends on the polling interval configured in your Latenode workflow.