How to Configure Make Snowflake Approval

Published
Length
3 min read

Luis Felipe Dias

All posts

You can build a make snowflake approval workflow by linking a chat trigger to a database role step. When a developer requests a role, Make sends a prompt to a manager and waits for a response. Teams often build this flow to stop sharing static database keys in chat channels. Without a review flow, admins often grant broad permissions that stay active for weeks. Those wide roles let anyone read or change production tables without oversight. How a native make snowflake approval workflow operates

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 can build a make snowflake approval workflow by linking a chat trigger to a database role step. When a developer requests a role, Make sends a prompt to a manager and waits for a response. Teams often build this flow to stop sharing static database keys in chat channels. Without a review flow, admins often grant broad permissions that stay active for weeks. Those wide roles let anyone read or change production tables without oversight.

How a native make snowflake approval workflow operates

The native flow starts when an engineer submits a form or chat message. Make catches this event through a webhook module and reads the user identity. Next, the workflow sends a message with approve and deny buttons to a reviewer. The scenario pauses until the reviewer clicks a button to confirm the request.

Once approved, Make uses a stored service account to run a role grant statement. That service account holds high privileges inside the Snowflake environment so it can manage permissions. You should set up a second timed branch in Make to revoke the role later. When the timer ends, Make runs a second statement that removes the user from the role. This two-step flow turns manual ticket queues into a quick automated routine.

Where role-level review leaves an operational gap

A workflow that grants a role only controls who can log in to the warehouse. Once the role is active, the database trusts every statement that user sends. An approved engineer might run a broad select query that pulls thousands of customer emails. They could also run an update statement without a filter and alter an entire table.

The automation tool also creates its own security risk for the data team. Make needs a strong service role in Snowflake to grant permissions to other users. If someone edits the Make scenario, they can use that service role to query tables. Also, chat logs only show who got the role and when the timer expired. They do not record the actual SQL statements the engineer ran during that session.

Approval Chains & Escalation + Snowflake Access Control: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

What to review before running queries in production

High-risk changes need inspection at the query level, not just at the role level. Before an alter or drop statement runs, a reviewer should see the exact SQL text. For routine read tasks, teams should apply data masking to rewrite sensitive fields in results. Masking replaces raw emails, phone numbers, card numbers, and national IDs with safe placeholders. Combining query-level checks with field masking keeps live data safe during every session.

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

How does Make authenticate to Snowflake to grant roles?

Make authenticates to Snowflake using a dedicated service user with a key pair or password. You must assign a security admin role to that user so it can grant roles.

What happens if the revoke step in Make fails to run?

If a network error stops the revoke module, the user keeps the Snowflake role. You should build an error handler in Make that alerts admins when a revoke fails.

Can a Make scenario approve individual SQL queries instead of roles?

You can send SQL text through Make for review and let the service account run it. Still, all queries then appear in Snowflake logs under the shared Make service account.

The query runs. The emails stay hidden.