Snowflake, ready to run.
The Snowflake integration lets a decision use what you already know. Floowed queries the history, the exposure and the reference tables your analysts have already modelled, and applies your rules to the answer.
What it does.
What Floowed reads from Snowflake
- Reference tables and lookups your rules depend on
- Customer or counterparty history, already joined and cleaned
- Exposure, limits and balances your team maintains
- Views built for the purpose, rather than raw tables
What it writes back
- The decision and its reasoning, into a table you own
- A row per case, so the outcome is queryable alongside everything else
The right shape here is usually a view rather than table access. Your team decides what a decision is allowed to see, we query that, and nothing wider is reachable. The role and warehouse are yours to grant and revoke.
A customer account change, from request to updated billing record.
- Gather
A customer asks in Zendesk to move billing to a new legal entity and attaches its registration document. Floowed pulls the account's history and open balance from a Snowflake view.
- Interpret
It reads the registration document and checks the entity name and registration number against the request.
- Chase
The tax ID is missing, so Floowed asks the requester on the ticket and waits for the answer.
- Decide
The policy engine runs your account-change rules on the balance and the history. An account outside them goes to finance operations, who decide.
- Act
Floowed updates the account in Salesforce and the customer in Stripe, writes a row for the case to a Snowflake table, and replies on the ticket.
Used in the same case
The connection, in detail.
How it connects.
- 1
Connect Snowflake
Using key-pair JWT, OAuth or a programmatic access token on a SERVICE user. Snowflake is removing password sign-in for service users. Nothing migrates and nothing is replaced.
- 2
Build your operation
Describe it in Slack, Teams or the Floowed Dashboard. Floowed builds it and asks only what it can’t work out.
- 3
Let it run
Every case runs from request to outcome, the same way each time, with the reasons on record. Anything sensitive waits for a person.
Questions
Does Floowed integrate with Snowflake?
Yes, over Snowflake's SQL API, using a role and warehouse your team creates for the purpose.
How does the Snowflake integration connect?
You create a role scoped to what a decision may read, grant it a warehouse, and set up key-pair authentication for it. Snowflake is retiring password sign-in for programmatic access, so a key pair or a programmatic access token is the right way in. Everything outside that grant is unreachable.
What can Floowed do with Snowflake data?
Warehouse data is usually the cleanest evidence a decision can get: history already joined, exposure already calculated. Floowed queries it, combines it with documents and external sources, and applies your rules.
Do I need to build anything in Snowflake?
A view and a role, which your data team can do in an afternoon. Nothing has to be modelled specially for us.
Is my Snowflake data secure?
Access is exactly the grant you make and revocable the same way. We would rather read a purpose-built view than have broader access we do not need.
What does the Snowflake integration cost?
Nothing extra from us. Integrations are included, and you pay for the work Floowed does on a case. Snowflake bills your own compute.
Start with Snowflake. Add the rest.
Free to try, no card, no sales call. Your first $80 of credits is on us.