Skip to content
Google BigQuery logoDrupal logo

Connect Google BigQuery to Drupal

Move data between Google BigQuery and Drupal 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.

Google BigQuery triggers
4
Google BigQuery actions
10
Drupal triggers
3
Drupal actions
6

Automation ideas

What you can build with Google BigQuery and Drupal

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

  • New Row in Google BigQuery creates Call Service in Drupal

    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.

  • Polling by ID in Drupal creates Run a Query in Google BigQuery

    A trigger that polls the Drupal site by ID.

  • New Row in Google BigQuery creates Create Entity in Drupal

    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.

  • Polling by ID in Drupal creates Create Row in Google BigQuery

    A trigger that polls the Drupal site by ID.

  • New Row in Google BigQuery creates List Entities in Drupal

    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.

  • Polling by ID in Drupal creates Create Rows in Google BigQuery

    A trigger that polls the Drupal site by ID.

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 Google BigQuery and acts in Drupal, 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.