Oracle Database

What it is

An Oracle connection lets SQL nodes run queries and statements against one service. Nodes reference the connection by name; the password itself is written to Honeybase's secret store at setup and is never returned by the API afterwards.

Before you start

• Know whether your listener expects a service name or an SID — that value goes in the database field.
• The listener must accept connections from Honeybase's egress addresses. If it sits in a private network, use the SSH tunnel described below.

Setup fields

These are the fields the guided setup collects — both the Add integration form and the setup card Barry raises in chat. Additional settings live on the connection's settings page once it exists.

Connection settings

Field	Type	Required	Secret	Notes
name	Text	Yes	No	Display name for this connection. This is what you pick from in a workflow node.
host	Text	Yes	No	Hostname or IP address of the database server, reachable from Honeybase.
port	Number	Yes	No	TCP port the listener is on. Oracle listeners use 1521 by default.
database	Text	Yes	No	The service name (or SID) to connect to — not a schema name.
username	Text	Yes	No	The Oracle user Honeybase authenticates as. Its default schema is what unqualified table names resolve against.
ssl	Toggle	No	No	Require TLS for the connection. Leave this on unless the listener genuinely has no TLS.

Credentials

Field	Type	Required	Secret	Notes
password	Password	Yes	Yes	The password for that user. Create a dedicated user for Honeybase rather than reusing an application account.

Configured after the connection exists

The guided setup does not ask for SSH tunnel, read-only mode, connection pool size, connection lifetime or query timeout. Open the connection on the Integrations page to change them.

Creating a user for Honeybase

CREATE USER honeybase IDENTIFIED BY "a-strong-generated-password";
GRANT CREATE SESSION TO honeybase;
GRANT SELECT ON app.orders TO honeybase;

Grant on specific objects rather than handing out SELECT ANY TABLE. Unqualified table names in your queries resolve against the connecting user's own schema, so either qualify them (app.orders) or create synonyms.

Read-only mode and the SSH tunnel

Read-only mode wraps every statement in a read-only transaction, so a node that tries to write against a read-only connection fails at the database.

SSH tunnel connects through a bastion host instead of directly. Turning it on reveals the public key to install on the bastion and the Honeybase IP ranges to allow through.