Skip to main content
Passwords are never accepted in an import link, and neither is anything else that decides where a credential comes from. What is left is the rest of the connection form, one query parameter per field, and a review sheet the user reads before anything is saved.
name, host and type are required. type takes any registered database type name, case-insensitive: MySQL, PostgreSQL, MongoDB, Redis, ClickHouse, Oracle, DuckDB, Cassandra, and every other type a loaded plugin registers. Enum-valued parameters must match a listed value exactly, since these are stored raw values rather than display names, and an unrecognized one falls back rather than failing the link. Percent-encode values that contain spaces: sslMode=Verify%20CA.

​
Core parameters

​
SSH parameters

Set ssh=1, or none of these are read.

​
SSL parameters

​
Driver fields

An af_ prefix passes a driver-specific field straight to the plugin: af_replicaSet=myrs sets replicaSet on a MongoDB connection. Field names come from the plugin, so the engine’s own page is where they are listed. Six field names are dropped on import, along with any name starting with aws, because each decides where a credential comes from: af_preConnectScript, af_preTunnelHost, af_preTunnelPort, af_promptForPassword, af_sslClientKeyPassphrase and af_usePgpass. The same rule covers .tablepro files, described in Connection Sharing. Add any of these by hand in the connection editor afterwards.

​
What the user sees

The review sheet shows the type, host and port, database, username, SSH auth method, SSL mode, color, tag, group, driver fields, and startup SQL. Only the name is editable. Add Connection saves it; when a connection with the same name, host, port and type is already there, the sheet warns “A connection with this name, host, and type already exists.” and the button becomes Add as Copy. The saved connection has no password, so open it in the connection editor and add one before connecting.