A MongoDB connection lets the MongoDB steps — Find documents, Insert a document, Insert documents, Update documents, Delete documents, Aggregate and Count — and the New document trigger work with your own MongoDB database, including MongoDB Atlas.

Who can do this

  • Workspace Admins and Editors, on every plan.

Before you start

  • A database user with a password. Bizomate signs in with a user name and password (SCRAM, MongoDB's usual sign-in). Make a user for Bizomate and give it a role only on the databases its workflows use — read to find and count, readWrite to insert, update and delete. Sign-in by certificate, cloud identity or Kerberos is not used.
  • Reachable from the internet. The database must have a public address. In Atlas, open Network Access and add Bizomate's addresses (below). A database on a private network or behind a VPN cannot be reached.
  • The connection string. In Atlas: your cluster › Connect › Drivers, then copy the string and put the user's password in place of <password>. It looks like mongodb+srv://bizomate:…@cluster0.ab1cd.mongodb.net/.

The addresses Bizomate connects from

If your database 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 MongoDB.
  3. In Connection name, type a name — for example Consulace orders.
  4. In Connection string, paste the string, with the password in it. "Stored encrypted. It is never shown again after you save."
  5. Optional: choose a date in This password expires on · optional if the password must be changed by then.
  6. Leave Test the connection before saving ticked.
  7. Select Save connection. It reads Testing while Bizomate signs in.

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

What happens next

  • The connection appears under Database. Every MongoDB step and the New document trigger list it under Connection.
  • Test signs in, pings the server and counts the databases the user can see, answering for example "Reached cluster0.ab1cd.mongodb.net · MongoDB 7.0.14, 3 databases".

Good to know

  • Bizomate allows 15 seconds to find and reach the database, and 30 seconds for each request.
  • Bizomate reaches only the public internet. Every server the connection uses — the ones in the string, and the ones the cluster names itself — is checked first.
  • The connection string is never shown again; to change it, Reconnect and paste the whole string again.

If something goes wrong

What you see Why What to do
MongoDB refused it — "MongoDB refused the user or password. Check the connection string on Connections." The user or password is wrong, or <password> is still in the string. Put the user's real password in the string.
"MongoDB did not answer. Check the connection string, and that the database's network access list lets Bizomate in." The database's network access list does not include Bizomate, or the address is wrong. In Atlas, add Bizomate's addresses under Network Access.
"… is not on the public internet, so workflows cannot reach it." The string names a private address. Use the database's public address.
"The connection string is not one MongoDB understands. It starts mongodb:// or mongodb+srv://. Replace it on Connections." What was pasted is not a MongoDB connection string. Copy it again from Atlas › Connect › Drivers.
"Use a MongoDB user and password in the connection string — authMechanism … signs in another way, which workflows cannot use." The string asks for a certificate, cloud identity or Kerberos sign-in. Make a database user with a password and use that.
"The connection string names a proxy, which workflows cannot use. …" The string has proxyHost. Take it out.