Skip to content
GitHub logoSnowflake logo

Connect GitHub to Snowflake

Move data between GitHub and Snowflake 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.

GitHub triggers
14
GitHub actions
19
Snowflake triggers
5
Snowflake actions
14

Automation ideas

What you can build with GitHub and Snowflake

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

  • New Pull Request in GitHub creates Run Query in Snowflake

    Triggers when there is activity on a pull request.

  • New Row in Snowflake creates Create Issue in GitHub

    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.

  • New Pull Request in GitHub creates Run Multiple Queries in Snowflake

    Triggers when there is activity on a pull request.

  • New Row in Snowflake creates Get issue information in GitHub

    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.

  • New Pull Request in GitHub creates Insert Row in Snowflake

    Triggers when there is activity on a pull request.

  • New Row in Snowflake creates Create comment on a issue in GitHub

    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.

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

Yes. Build one flow that starts in GitHub and acts in Snowflake, 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.