Can Snowflake and Greip talk in both directions?

Yes. Build one flow that starts in Snowflake and acts in Greip, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.

Connect Snowflake to Greip

Move data between Snowflake and Greip the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

Start building Explore Snowflake Explore Greip

Snowflake triggers: 5
Snowflake actions: 14
Greip triggers: 5
Greip actions: 6

Automation ideas

What you can build with Snowflake and Greip

A few flows teams run between Snowflake and Greip. Use one as a starting point, or build your own from scratch.

New Row in Snowflake creates ASN Lookup in Greip
Triggers when a new row is inserted into the selected table. Uses a timestamp column you choose to detect rows added since the last check.
Proxy Connection Detected in Greip creates Run Query in Snowflake
Triggers when a new proxy connection is detected
New Row in Snowflake creates BIN Lookup in Greip
Triggers when a new row is inserted into the selected table. Uses a timestamp column you choose to detect rows added since the last check.
Proxy Connection Detected in Greip creates Run Multiple Queries in Snowflake
Triggers when a new proxy connection is detected
New Row in Snowflake creates IP Lookup in Greip
Triggers when a new row is inserted into the selected table. Uses a timestamp column you choose to detect rows added since the last check.
Proxy Connection Detected in Greip creates Insert Row in Snowflake
Triggers when a new proxy connection is detected