A PostgreSQL connection lets the PostgreSQL · Query step run SQL against your own database. You give Bizomate the server's address, the database, and a user and password of your own; Bizomate signs in as that user.

Who can do this

Workspace Admins and Editors, on any plan — PostgreSQL is not a premium connection.

Before you start

  • A user of its own. Make a PostgreSQL user for Bizomate and give it only the tables your workflows need. "A PostgreSQL user of your own. Give it only the tables your workflows need." It signs in with a user name and password.
  • Reachable from the internet. The server must have a public address, and its firewall must let Bizomate in on the port (5432 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 PostgreSQL. It reads "Stored credential".
  3. In Connection name, type a name — for example Orders database.
  4. In Server, type the server's address, with the port after a colon if it is not 5432 — for example consulace-db.postgres.database.azure.com:5432.
  5. In Database, type the database's name — for example orders.
  6. In User, type the user Bizomate signs in as.
  7. In Password, type that user's password. "Stored encrypted. It is never shown again after you save."
  8. Optional: if the password must be changed by a date, choose it in This password expires on · optional. The workspace's admins are reminded 30, 7 and 1 days before.
  9. Leave Test the connection before saving ticked.
  10. Select Save connection. It reads Testing while Bizomate signs in.

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

What happens next

  • The connection appears under Database. Its panel shows Server — "consulace-db.postgres.database.azure.com · orders" — and never the user or password.
  • The PostgreSQL · Query step lists it under Connection.
  • Test signs in and runs select 1, answering "Signed in to PostgreSQL."

Good to know

  • Bizomate allows 15 seconds to connect.
  • What is stored is a connection string made from your fields, encrypted. Fields are never shown again; to change any of them, Reconnect and fill all four in again.
  • An IPv6 address goes in square brackets, with the port after: [2001:db8::1]:5432.

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.
"The port after the colon is not a number between 1 and 65535." The port is mistyped. Correct it, or leave it off for 5432.
"One of these is longer than a database accepts." A field is too long. Check what you pasted.
PostgreSQL refused it — "PostgreSQL refused: … Nothing was saved." The server turned the sign-in down, or could not be reached in 15 seconds. Check the user, password and database; check the firewall allows outside connections on the port.
"consulace-db.internal is not on the public internet, so workflows cannot reach it." The address is a private one. Use the server's public address.
"consulace-db.example.com could not be found." The name does not exist on the internet. Check the address.
"Use a PostgreSQL user and password in the connection string — Username=…;Password=… — and no Passfile setting." The stored connection does not sign in with a user and password. Reconnect with a user and password.