How to Configure Flowise ClickHouse Credentials
You set up flowise clickhouse credentials by making a scoped database user and adding those details to your app. First, create a ClickHouse user with strict read permissions, then store the login details in Flowise. Many teams rush this step and share a main admin account instead. That broad role lets an AI workflow read or change every table in the cluster. A bad prompt or a simple bug can then expose private rows or drop key tables. How to set up flowise clickhouse credentials with SQL roles
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 flowise clickhouse credentials by making a scoped database user and adding those details to your app. First, create a ClickHouse user with strict read permissions, then store the login details in Flowise. Many teams rush this step and share a main admin account instead. That broad role lets an AI workflow read or change every table in the cluster. A bad prompt or a simple bug can then expose private rows or drop key tables.
How to set up flowise clickhouse credentials with SQL roles
ClickHouse treats users, roles, row policies, settings profiles, and quotas as access entities. You can create and manage all of these entities with SQL statements. To turn on SQL access control, the server needs a storage folder path set up. You also need at least one admin account with user management rights turned on. Remember that a database user can only grant rights that they already hold themselves.
Creating a new user for Flowise requires the user creation privilege in ClickHouse. During user creation, you pick the login method and set the allowed client hosts. You also assign default roles and specific per-user settings in that same step. Locking the host list to your Flowise server IP blocks outside login attempts right away.
Next, you grant read rights only on the tables and columns your AI workflow needs. ClickHouse lets you grant read access on single columns within a specific table. The Flowise user can then query those allowed columns, while other columns stay off limits. If the app runs a wildcard query for all columns, ClickHouse refuses the query. A wildcard query only works if the user has rights to every column in that table by default. Since version 24.10, a trailing asterisk lets you grant rights across tables that share a name prefix.
What native database roles solve and what they leave open
Native ClickHouse roles and column grants solve the first part of database safety. They decide who can log in and which tables or columns that account can read. Host checks and quotas also keep basic abuse in check at the database level.
Ephemeral Credentials + ClickHouse Access Management: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
Still, static credentials inside Flowise leave big operational gaps open during daily runs. Once Flowise logs in, the database trusts every query that passes the basic column check. Static passwords sit in the app database and rarely get rotated on a set schedule. Everyone sharing that Flowise workspace uses the exact same underlying database identity for every run.
Database grants also cannot inspect what happens inside the data rows during a live query. An allowed text column might still hold emails, phone numbers, card numbers, or national IDs. Standard column grants return those raw values straight into the AI prompt context. Native roles decide who logs in, not what individual statements return in flight. When an AI agent runs a risky query, no native step pauses it for human review. Audit logs only show the shared Flowise user, not the human who triggered the chat.
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 wildcard query fail after setting column grants for Flowise?
ClickHouse blocks wildcard queries when a user only has rights to some columns in a table. Change the Flowise query to name the allowed columns directly, or grant access to all columns by default.
How can I grant Flowise access to many tables with the same prefix?
Since ClickHouse version 24.10, you can put a trailing asterisk at the end of a table prefix. This grants read rights across all tables that start with that exact name pattern.
What happens if an allowed ClickHouse column holds sensitive user details?
Column grants are all or nothing, so ClickHouse returns the full text to Flowise. You need data masking to rewrite emails, phone numbers, card numbers, or national IDs in results.
Related guides
In this post