Skip to main content
This example demonstrates how to trigger a run that processes data already loaded into a relational database like PostgreSQL or Snowflake. Scenario: An external process loads invoice data into a raw_invoices table in your PostgreSQL database. All records for a given batch are tagged with the same batch_id. The Flow Version invoice_processor:v1 is configured in the Lume UI with:
  • Source Connector: Your PostgreSQL database.
  • Source Tables: raw_invoices.
  • Filtering Logic: A WHERE clause like batch_id = '{source_path}'.
  • Target Connector: Your Snowflake data warehouse.
  • Target Table: clean_invoices.

Sample Input

(Records in the PostgreSQL raw_invoices table where batch_id matches the source_path)

Sample Output

(New records created in the Snowflake clean_invoices table by the Lume pipeline) Notice how the Flow Version transformed the data: it standardized IDs, converted the amount to cents, and added a processing timestamp.
For production workflows, consider using Webhooks instead of run.wait() for more efficient, event-driven monitoring.

Final Result