About the Database Hub connector

Integration Service connector for Database Hub in Automation Cloud, supporting SQL Server, PostgreSQL, Oracle, Redshift, and Databricks for CRUD operations, custom SQL, and triggers.

A database connector supporting popular JDBC-compatible databases such as SQL Server, PostgreSQL, Oracle, Redshift, and Databricks for secure CRUD, custom SQL queries, and triggers.

Authentication

Before automating processes, you need to establish a connection with your database. Step-by-step instructions are available in the Database Hub authentication page.

Events

The connector supports Record Created and Record Updated events on SQL Server, Oracle, PostgreSQL, Databricks, and Redshift. To activate triggers, your tables must meet the table eligibility and database-specific prerequisites. For details, see the Triggers page.

Activities

You can use the connection to build automations that execute queries, insert and update records, and manage database tables. For more information, visit the Database Hub activities page.

Provider documentation

Find more information about supported databases from their official documentation:

• Microsoft SQL Server documentation
• PostgreSQL documentation
• Oracle Database documentation
• Amazon Redshift documentation
• Databricks documentation

Known issues

• In the filter builder, date and time values selected with the date-time widget might not be sent in the expected format (the pattern mask is not applied), which can cause the filter query to fail.
• A custom expression entered manually for a date-time field is not reflected in the filter builder UI.

As an alternative, use the Execute Query Synchronously activity with a valid SQL statement to apply the date and time filter directly, instead of the filter builder.

Frequently asked questions

Why are the Get Record, Update Record, and Delete Record activities not available for my table?

These record-level activities identify rows by their primary key, so the target table must have a primary key defined. For tables without a primary key, use the Execute Query Synchronously activity to run custom SQL instead.

Why are some fields missing from my query results?

Fields that contain null values are omitted from the connector's responses. This is expected behavior — automation logic should treat an absent field as a null value rather than expecting an explicit null in the output.