How to Configure Make ClickHouse Connect

Published
Length
3 min read

Luis Felipe Dias

All posts

You set up a make clickhouse connect workflow by creating a database user and adding its credentials to your Make scenario. This lets your automation scenarios send queries and read analytics data over a network link. Many teams start by using a single shared admin account for all their automation steps. That broad setup gives every scenario full power to read or change any table. A bad query in one scenario can expose private data or drop rows across the cluster. How to set up a make clickhou

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 a make clickhouse connect workflow by creating a database user and adding its credentials to your Make scenario. This lets your automation scenarios send queries and read analytics data over a network link. Many teams start by using a single shared admin account for all their automation steps. That broad setup gives every scenario full power to read or change any table. A bad query in one scenario can expose private data or drop rows across the cluster.

How to set up a make clickhouse connect user

A safer setup starts inside the database with SQL-driven access control. ClickHouse manages users, roles, row policies, settings profiles, and quotas as access entities. You first turn on SQL access control by setting a server storage directory. You also need an admin user with access management rights turned on. Remember that a user can only grant the privileges that they hold themselves.

With that ready, you create a dedicated user just for your Make scenarios. Creating a user requires the create user privilege on the database. In that step, you pick the login method and set the allowed client hosts. You also assign default roles and apply per-user settings for that automation account. Next, you limit which tables and columns the automation user can read. ClickHouse lets you grant select rights on specific columns in a table. The user can then query only those named columns. If a scenario runs a select-all query, the database refuses it and returns no data. That select-all query only works when the table holds just the granted columns. In newer versions, a trailing asterisk also lets you grant rights by table name prefix.

Where native database roles fall short for automation

Native roles and column grants do a great job of limiting who logs in. They also lock down which tables and columns a static user can touch. Still, static database credentials stored in a workflow tool still create blind spots. Every scenario that shares the same connection profile runs as the same database user. Your database logs show the shared automation user, not the builder who changed the scenario.

Column grants are also all-or-nothing rules at the schema level. Sometimes a scenario needs to read a table that holds emails, phone numbers, or card numbers. If you block the column, the scenario breaks when it tries to read a wide row. If you allow the column, raw emails and national IDs flow straight into external apps. Static roles also cannot require a quick human check before a scenario runs a write query. Once the user has write rights, every scenario step can run changes at any time.

ClickHouse Access Management + End-to-End Encryption: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

Managing query behavior in flight

Teams get better control when they inspect queries in flight instead of relying only on static logins. Rather than storing long-lived admin keys inside third-party tools, you can check each query as it runs. Dynamic data masking can rewrite matched fields like emails or phone numbers in query results. The automation scenario still gets a valid response, so the workflow does not break. You can also tie each connection back to a real team identity and log every statement.

Check ClickHouse queries and result columns on the wire

ClickHouse users and row policies decide who connects. They do not check each statement on the wire or redact sensitive string columns in query results. With hoop.dev, you run an open-source proxy, a sidecar for your ClickHouse. It reads ClickHouse's native TCP protocol before queries run while ClickHouse stays in charge of login and grants.

Multi-statement queries and table mutations are split and checked by hoop.dev guardrails. Banned actions are refused with a native ClickHouse error. On returned rows, hoop.dev data masking rewrites String and FixedString columns that match your rules. The audit trail logs each query, table, and verdict. See the MIT-licensed source on GitHub.

Frequently asked questions

Why did my select-all query fail in a Make scenario?

ClickHouse blocks select-all queries when a user only has grants on specific columns. Update your scenario to list only the allowed column names in the query.

Can I restrict which IP addresses my automation user logs in from?

Yes, the create user statement in ClickHouse lets you define allowed client hosts. The database will reject login attempts from any host outside that list.

How do I stop scenarios from reading raw emails or card numbers?

You can remove select rights on those columns using native SQL grants. If the query still needs those columns present, use data masking to rewrite the fields in results.

The query runs. The emails stay hidden.