Skip to content
Google BigQuery logoTeamleader logo

Connect Google BigQuery to Teamleader

Move data between Google BigQuery and Teamleader 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
Teamleader triggers
5
Teamleader actions
13

Automation ideas

What you can build with Google BigQuery and Teamleader

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

  • New Row in Google BigQuery creates Create Contact in Teamleader

    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 Contact in Teamleader creates Run a Query in Google BigQuery

    Triggers when a new contact is created

  • New Row in Google BigQuery creates Update Contact in Teamleader

    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 Contact in Teamleader creates Create Row in Google BigQuery

    Triggers when a new contact is created

  • New Row in Google BigQuery creates Create Company in Teamleader

    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 Contact in Teamleader creates Create Rows in Google BigQuery

    Triggers when a new contact is created

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 Teamleader, 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.