Skip to content
Omni logoGoogle BigQuery logo

Connect Omni to Google BigQuery

Move data between Omni and Google BigQuery the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

Omni triggers
0
Omni actions
9
Google BigQuery triggers
4
Google BigQuery actions
10

Automation ideas

What you can build with Omni and Google BigQuery

A few flows teams run between Omni and Google BigQuery. Use one as a starting point, or build your own from scratch.

  • New Row in Google BigQuery creates Create a document in Omni

    Triggers when a new row is added to a BigQuery table. Polls every 5 minutes by comparing the latest value in a sort column against the previous check.

  • New Row in Google BigQuery creates Create a schedule in Omni

    Triggers when a new row is added to a BigQuery table. Polls every 5 minutes by comparing the latest value in a sort column against the previous check.

  • New Row in Google BigQuery creates Delete a document in Omni

    Triggers when a new row is added to a BigQuery table. Polls every 5 minutes by comparing the latest value in a sort column against the previous check.

  • Updated Row in Google BigQuery creates Create a document in Omni

    Triggers when an existing row is updated in a BigQuery table. Requires an `updated_at` TIMESTAMP column that is set whenever a row changes.

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

Yes. Build one flow that starts in Omni and acts in Google BigQuery, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.