How to Configure Zapier Bigquery Read Only Access
You set up zapier bigquery read only access by pairing a viewer role with a job runner role. This lets the automation tool run queries and read tables without editing data. Many teams skip this step when they build fast workflows. They log in with a broad owner account to make the workflow work right away. That shortcut gives every shared automation full power to change or delete production tables. A good setup scopes permissions down to the exact datasets that the workflow needs. How to set
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.
You set up zapier bigquery read only access by pairing a viewer role with a job runner role. This lets the automation tool run queries and read tables without editing data.
Many teams skip this step when they build fast workflows. They log in with a broad owner account to make the workflow work right away. That shortcut gives every shared automation full power to change or delete production tables. A good setup scopes permissions down to the exact datasets that the workflow needs.
How to set up zapier bigquery read only access
Google Cloud splits data viewing and query running into two separate permission groups. First, the account needs permission to start a query job inside the cloud project. Without job permissions, the database rejects every query before it even checks the tables. Second, the account needs viewer permissions on the specific dataset or table it reads.
Start by creating a dedicated cloud identity just for your automation tasks. Never reuse a personal engineer account for background jobs. Assign the job runner role at the project level so the identity can submit queries. Next, open the target dataset and grant data viewer permissions to that same identity.
Now connect the automation tool using that restricted cloud identity. When a workflow triggers, the tool sends a query job to the project. The cloud platform checks the job role first, then checks the dataset viewer role. If the workflow tries to insert rows or drop a table, the database blocks it.
What native roles solve and where gaps remain
Project and dataset roles stop accidental writes and table drops from automated workflows. They also keep third-party apps from reading other datasets in the same cloud project. For basic reporting tasks, dataset viewer permissions handle the main risk of data loss.
Still, static cloud roles only decide who can log in and which tables open. They do not inspect the actual queries running inside the session. Once a workflow has viewer rights on a table, it reads every column inside it. If that table holds emails, phone numbers, or card numbers, the workflow pulls them all.
Auditor Read-Only Access + Customer Support Access to Production: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
Shared automation platforms make this column gap much worse. Many team members can edit a workflow and change the query text at any time. One broad query can pull thousands of private rows and send them to external apps. Cloud audit logs record that the shared identity ran a query, not which builder triggered it.
Why teams restrict query results and shared keys
Long-lived keys and OAuth tokens stay active in third-party tools until someone revokes them. If an engineer leaves the company, workflows tied to their login often break or stay exposed. Rotating these keys by hand across dozens of active workflows takes hours of careful work.
Security teams also need a way to protect sensitive fields during read queries. Creating separate cloud views for every single workflow adds heavy upkeep for data engineers. Teams want to rewrite emails and card numbers in query results before data leaves the warehouse. They also need clear logs that tie every query back to a specific purpose.
Govern statements and responses across databases and APIs
Good config and scoped roles are needed setup. They do not check single queries in flight or mask sensitive fields in returned rows. Across Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes APIs, SSH, and internal HTTP endpoints, hoop.dev runs beside each supported service as an open-source proxy, a sidecar for your database or API.
First, hoop.dev guardrails block banned queries before they run. Then hoop.dev data masking rewrites matched sensitive values in responses in memory. The audit trail records every statement and verdict per resource. Furthermore, hoop.dev holds SOC 2 Type II and is open source on GitHub.
Frequently asked questions
Why does a read-only account still need job permissions in BigQuery?
BigQuery treats every SQL query as a compute job that uses project resources. Viewer roles allow data reading, while job roles allow the account to run the query.
Can I limit a workflow to one single table instead of a whole dataset?
Yes, you can grant the data viewer role on a single table instead of the dataset. The account still needs project job permissions to run the select statement.
What happens if a read-only workflow tries to insert new rows?
The database blocks the write request and returns a permission error to the automation tool. Your existing table data stays safe and unchanged.
Related guides
In this post