UiPath Documentation
activities
latest
false
Integration Service activities

Triggers

Triggers included in the Database Hub connector, available via polling for record created and record updated changes across supported JDBC databases.

These triggers detect changes via polling:

TriggerDescription
Record CreatedTriggers when a new record is added to a table.
Record UpdatedTriggers when an existing record is modified.

Triggers are supported on the following databases: SQL Server, Oracle, PostgreSQL, Databricks, and Redshift.

How it works​

Triggers use a polling mechanism that checks your database tables for changes at regular intervals (every five minutes, by default). The polling interval is configured at the connection level, so changing it affects all triggers associated with that connection. For details, refer to the Triggers documentation.

Once you enable triggers on a connection, the connector automatically detects which tables are eligible, using one of two change-tracking methods:

  1. Native change tracking — If the database has built-in change tracking enabled (for example, SQL Server Change Tracking or Databricks Change Data Feed), the connector uses it automatically. This provides the most accurate detection of inserts versus updates.
  2. Timestamp-based detection — If native change tracking is not available, the connector falls back to common audit timestamp columns in your tables (for example, UpdatedDate, ModifiedAt, CreatedDate).

A table is eligible for triggers if it supports either of these methods.

Note:

Tables must also have a primary key defined to be eligible for triggers.

Database-specific prerequisites​

What you do to activate triggers depends on whether your database supports native change tracking:

DatabaseNative change trackingWhat to do to activate triggers
SQL ServerYes (recommended)Enable Change Tracking: ALTER TABLE ... ENABLE CHANGE_TRACKING. Otherwise, the connector uses an audit timestamp column.
DatabricksYes (recommended)Enable Delta Lake Change Data Feed: ALTER TABLE ... SET TBLPROPERTIES (delta.enableChangeDataFeed = true). Otherwise, the connector uses an audit timestamp column.
OracleNoAdd an audit timestamp column (for example, ModifiedAt).
PostgreSQLNoAdd an audit timestamp column (for example, ModifiedAt).
RedshiftNoAdd an audit timestamp column (for example, ModifiedAt).

Filtering​

When you configure a trigger, you can open the Filter builder to narrow which records trigger the automation (for example, only records where status = 'active').

Tips for best results​

  • Native change tracking provides the most reliable detection when enabled.
  • Tables with a primary key are eligible for triggers.
  • Commonly named audit columns (UpdatedDate, ModifiedDate, CreatedDate, ModifiedAt) are recognized automatically.
  • The Filter builder limits triggers to only the relevant records.

All triggers are automatically accessible under the Wait for an Event and Resume activity for your long-running workflows. For details, refer to Long-running workflows with Integration Service activities.

  • How it works​
  • Database-specific prerequisites​
  • Filtering​
  • Tips for best results​

Was this page helpful?

Connect

Need help? Support

Want to learn? UiPath Academy

Have questions? UiPath Forum

Stay updated