How to Configure Make Bigquery Approval

Published
Length
3 min read

Luis Felipe Dias

All posts

To set up a make bigquery approval flow, pause the scenario until a reviewer clicks a webhook link. After the reviewer approves the request, the next module runs your SQL query in Google Cloud. Teams often link Make to their data warehouse with one shared service account. When that account has broad roles, any scenario can read or change sensitive tables. How a native make bigquery approval workflow runs Make connects to Google Cloud through OAuth user logins or service account keys. Most tea

Your coding agents run with your access.

Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.

To set up a make bigquery approval flow, pause the scenario until a reviewer clicks a webhook link. After the reviewer approves the request, the next module runs your SQL query in Google Cloud. Teams often link Make to their data warehouse with one shared service account. When that account has broad roles, any scenario can read or change sensitive tables.

How a native make bigquery approval workflow runs

Make connects to Google Cloud through OAuth user logins or service account keys. Most teams create one service account in Google Cloud IAM for all Make scenarios. They assign roles that let this account run jobs and read datasets.

Make does not have a single built-in pause button for human review. Instead, builders split the workflow into two separate scenarios. The first scenario catches the trigger event and builds the SQL text. It sends a message to a chat app or email with an approval link. That link points to a custom webhook in the second scenario.

The first scenario also writes the pending query details into a data store. When a manager clicks the approval link, the second scenario wakes up. It reads the stored query details and checks who clicked the link. Then it sends the SQL job to the data warehouse using the stored Google Cloud key.

Where native roles and webhook steps fall short

This two-part webhook design solves basic scheduling needs for small teams. It stops automated tasks from running before a human checks the request. Google Cloud IAM roles also block unauthorized outside accounts from logging in. Yet this setup leaves large security gaps during the actual query run.

First, the service account key sits inside the automation platform as a static secret. Anyone who can edit scenarios in that workspace can use that same key. They can build a new scenario that skips the webhook approval step altogether. Google Cloud only sees the service account identity, not the human who built the flow.

Approval Chains & Escalation + BigQuery IAM: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

Second, IAM roles decide who can log in, not what individual queries do in flight. A role that allows table updates allows updating one row or wiping the whole table. If a dynamic variable in Make breaks, the approved query might pull way too much data.

Why data masking and query checks matter

Automated workflows often pull customer records to send emails or update support tickets. Even when a manager approves a run, the query results might hold private fields. Raw emails, phone numbers, card numbers, and national IDs then flow into Make execution logs. Every person with access to the Make dashboard can read those saved bundle payloads.

Native warehouse roles operate at the table or column level for the whole service account. You cannot easily change masking rules per scenario without making dozens of service accounts. Teams need a way to inspect each SQL statement right before it runs. They also need a way to rewrite matched fields in results before data reaches the automation logs.

Add runtime guardrails and masking beside your databases and APIs

Login rules, role grants, and CI checks govern who connects to your stack. Yet any allowed script, engineer, or AI agent still runs commands with the full scope of its role. For workloads on Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes, SSH, or internal HTTP services, hoop.dev sits beside the service as an open-source proxy, a sidecar for your database or API.

Before a query runs, hoop.dev guardrails check the statement against your rules. An AI Analyzer you configure can score intent or hold risky calls for human review. Next, hoop.dev data masking rewrites sensitive fields in responses, and each verdict is logged per listener. Explore the MIT-licensed project on GitHub.

Frequently asked questions

Can Make pause a single scenario and wait for human approval?

Make scenarios time out if they wait too long for a response. You must split the flow into two scenarios linked by a webhook and a data store.

How should we scope Google Cloud IAM roles for Make scenarios?

Create a dedicated service account for Make with the smallest possible dataset permissions. Avoid project-wide admin roles, and grant read or write access only to specific tables.

Why do sensitive fields show up in Make execution history?

Make logs the full output bundle of every module by default for debugging. Unless you mask emails or card numbers before they arrive, they stay visible in the logs.

The query runs. The emails stay hidden.