How to Configure Make Bigquery Credentials
You set up make bigquery credentials by linking a Google Cloud identity to your workflow app. You can log in with a personal account or upload a service account key file. Most teams pick a single service account so workflows keep running when staff changes happen. Yet teams often give that account broad project roles to avoid permission errors during testing. Those wide roles let any workflow read or change every table in the warehouse. How make bigquery credentials work in cloud workflows Ma
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 make bigquery credentials by linking a Google Cloud identity to your workflow app. You can log in with a personal account or upload a service account key file. Most teams pick a single service account so workflows keep running when staff changes happen. Yet teams often give that account broad project roles to avoid permission errors during testing. Those wide roles let any workflow read or change every table in the warehouse.
How make bigquery credentials work in cloud workflows
Make runs cloud tasks by sending API calls to your Google Cloud project. First, you create a custom connection inside your Make workspace. For team tasks, you make a service account inside Google Cloud. That account acts like a robot user with its own mail address and key. You grant that account roles to run jobs and read specific datasets.
Next, you generate a private key file and upload it to Make. Make stores this secret and uses it to sign token requests. When a scenario runs, Make trades that signed request for a short token. Google Cloud checks the token and checks the role attached to the service account. If the role allows the task, BigQuery runs the query and returns the rows.
Why static keys create risk for data teams
Native service account keys solve the basic problem of unattended login. Your scheduled workflows can run at night without a human clicking a login prompt. Google Cloud IAM also lets you block access to unrelated cloud tools like storage buckets.
Still, this native setup leaves a major security gap open during daily runs. Cloud roles only check who logs in at the start of a session. They do not inspect what each query does while it runs in flight. If a workflow has write access, a bad prompt or bug can drop a table.
Static keys also create a tracking problem for security teams. Many different workflows often share the same make bigquery credentials to save setup time. Every query in the cloud log shows the exact same robot user name. When a bad query spikes costs or pulls sensitive data, you cannot find the source. Also, raw results flow straight back into the workflow memory. Sensitive fields like emails, phone numbers, or card numbers sit exposed in run histories.
Ephemeral Credentials + BigQuery IAM: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
Steps to lock down your workflow roles
You can reduce risk by shrinking what each service account can touch. Never assign project-wide admin or editor roles to a workflow key. Instead, grant job user permissions at the project level so the app can run queries. Then grant data viewer or data editor permissions on the single dataset needed.
Create separate service accounts for different teams or high-risk workflows. This habit keeps finance data separate from marketing automation tasks. Rotate your downloaded key files on a set schedule and delete old keys right away. Even with tight dataset roles, native cloud settings cannot filter individual columns or mask results. You must still watch out for broad select queries that pull private customer records.
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
Should I use a personal login or a service account for Make?
Use a service account for any shared or production workflow. Personal logins break when a user changes their password or leaves the company. Service accounts stay active and let you set tight dataset rules.
What minimum roles do make bigquery credentials need?
The account needs permission to create query jobs in your cloud project. It also needs read or write access on the target dataset. Avoid granting broad project roles that manage every table at once.
How do I stop workflows from pulling sensitive customer columns?
Native dataset roles apply to whole tables unless you build complex policy tags. You can either point workflows at safe views or filter data during the query run. Masking rules can also rewrite emails, phone numbers, and card numbers in query results.
Related guides
In this post