Skip to content
GitLab logoSnowflake logo

Connect GitLab to Snowflake

Move data between GitLab 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.

GitLab triggers
1
GitLab actions
2
Snowflake triggers
5
Snowflake actions
14

Automation ideas

What you can build with GitLab and Snowflake

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

  • New Project Issue Event in GitLab creates Run Query in Snowflake

    Triggers on project issue events when an issue is created or when an existing issue is updated, closed, or reopened.

  • New Row in Snowflake creates Create Issue in GitLab

    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 Project Issue Event in GitLab creates Run Multiple Queries in Snowflake

    Triggers on project issue events when an issue is created or when an existing issue is updated, closed, or reopened.

  • New Row in Snowflake creates Custom API Call in GitLab

    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 Project Issue Event in GitLab creates Insert Row in Snowflake

    Triggers on project issue events when an issue is created or when an existing issue is updated, closed, or reopened.

  • New or Updated Row in Snowflake creates Create Issue in GitLab

    Triggers when a row is inserted or updated in the selected table. Uses an "updated at" timestamp column you choose — any row whose timestamp is newer than the last check will fire the trigger.

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 GitLab 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.