A MySQL connection lets the MySQL steps — Run a query, Insert rows, Update rows, Delete rows, Find rows and Run a stored procedure — and the New row trigger work with your own MySQL or MariaDB database. You give Bizomate the server, the database, and a user and password of your own.

Who can do this

  • Workspace Admins and Editors.
  • Plan: MySQL is a premium connection. You can add it and test its steps on any plan; publishing a workflow that uses it needs Starter, Pro or Enterprise.

Before you start

  • A MySQL user. Bizomate signs in with a user name and password. Make a user for Bizomate and give it only the tables your workflows need — SELECT to read, and INSERT, UPDATE or DELETE only where a step changes rows. The user must be allowed to sign in from outside the server (a host of %, or Bizomate's addresses below), not only from localhost.
  • Encryption. Bizomate connects with TLS unless you choose otherwise. MySQL 8, Azure Database for MySQL, Amazon RDS and Aurora all accept TLS. Some MariaDB servers have none set up; for those, choose If the server offers it.
  • Reachable from the internet. The server must have a public address, and its firewall must let Bizomate in on its port (3306 unless you changed it). A server on a private network or behind a VPN cannot be reached. If the firewall allows only listed addresses, add Bizomate's (below).

The addresses Bizomate connects from

If your server's firewall only lets in addresses you list, add all of these. Bizomate connects from one of them, and which one can change without notice, so allow every one:

20.244.77.107, 98.70.233.34, 98.70.238.182, 4.187.192.56, 4.187.192.83, 4.187.202.192, 4.247.208.118, 4.188.89.53, 20.235.194.47, 135.13.177.151, 135.13.180.237, 4.224.138.26, 4.224.139.74, 4.188.89.72, 4.247.208.154, 4.224.71.1, 4.188.115.70, 4.187.190.117, 20.219.174.118, 20.204.214.217, 4.247.214.195, 4.247.236.85, 4.247.215.225, 4.224.71.224, 4.224.115.37, 4.224.115.87, 4.187.214.53, 4.187.204.15, 20.204.211.52, 20.204.214.68, 20.192.171.20

These are the outgoing addresses of Bizomate's servers in Azure Central India (as of 2 October 2026). If they change, this article is updated.

Steps

  1. Select Connections in the bar at the top, then + Add connection.
  2. Under Database, select MySQL. It reads "Stored credential", with the diamond for paid plans.
  3. In Connection name, type a name — for example Consulace CRM.
  4. In Server, type the server's address, as the example shows: db.consulace.com:3306. Leave off the port for 3306; add it after a colon for any other.
  5. In Database, type the database's name.
  6. In User, type the user. "A MySQL user of your own. Give it only the tables your workflows need."
  7. In Password, type that user's password. "Stored encrypted. It is never shown again after you save."
  8. In Encryption, leave Always encrypted (TLS) unless the server has no TLS. "Keep it always encrypted unless the server has no TLS — then your password crosses the internet unencrypted."
  9. Optional: choose a date in This password expires on · optional if the password must be changed by then.
  10. Leave Test the connection before saving ticked.
  11. Select Save connection. It reads Testing while Bizomate signs in.

The toast "Connection added" says "“Consulace CRM” is ready. Every workflow in this workspace can use it."

What happens next

  • The connection appears under Database. Its panel shows Server — "db.consulace.com · crm" — and never the user or password.
  • Every MySQL step and the New row trigger list it under Connection.
  • Test signs in and reads the server's version, answering for example "Reached crm on db.consulace.com · MySQL 8.0.36" — or "· MariaDB 10.11.6" for MariaDB.

Good to know

  • On the Free plan the window notes: "MySQL is on paid plans. You can add it and test the steps that use it now; publishing a workflow that uses it asks for a paid plan."
  • Bizomate allows 15 seconds to connect and 30 seconds for each statement.
  • Bizomate reaches only the one server you name: no failover list, no redirection to another server, and no file of the server's choosing is ever read.
  • Fields are never shown again; to change any of them, Reconnect and fill them all in again.

If something goes wrong

What you see Why What to do
"Give the server's address.", "Give the database's name.", "Give the user it signs in as.", "Give the user's password." That field is empty. Fill it in.
MySQL refused it — "MySQL refused the user or password. Check them on Connections — and that the user may sign in from outside the server." The password is wrong, or the user may sign in only from the server itself. Check the password; give the user a host of % or Bizomate's addresses.
"MySQL did not answer: … Check the server and port on Connections, and that its firewall lets Bizomate in." The server's firewall did not let Bizomate in, or the address or port is wrong. Allow Bizomate's addresses on the server's port; check the address.
"MySQL's encryption did not work. If the server has no TLS, choose “If the server offers it” under Encryption on Connections." The server has no TLS set up. Set up TLS on the server, or reconnect with If the server offers it.
"… is not on the public internet, so workflows cannot reach it." The address is a private one. Use the server's public address.
"… could not be found. Check the server on Connections." The address does not exist. Check the spelling of the server's address.