Skip to content
IMAP logoGoogle BigQuery logo

Connect IMAP to Google BigQuery

Move data between IMAP 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.

IMAP triggers
1
IMAP actions
4
Google BigQuery triggers
4
Google BigQuery actions
10

Automation ideas

What you can build with IMAP and Google BigQuery

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

  • New Email in IMAP creates Run a Query in Google BigQuery

    Trigger when a new email is received

  • New Row in Google BigQuery creates Mark Email as Read/Unread in IMAP

    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 Email in IMAP creates Create Row in Google BigQuery

    Trigger when a new email is received

  • New Row in Google BigQuery creates Copy Email in IMAP

    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 Email in IMAP creates Create Rows in Google BigQuery

    Trigger when a new email is received

  • New Row in Google BigQuery creates Move Email in IMAP

    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.

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 IMAP 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.