SnapLogic Git Integration


With the Git Integration, you can track, update, and manage versions of SnapLogic project files, pipelines, tasks, and accounts, using either the SnapLogic graphical interface or the SnapLogic Public APIs. These operations include checkout, add, remove, pull, and commit, as well as creating branches and tags. Refer to Git operations for more information.

Gitflow and trunk-based development are two common ways of managing concurrent development and asset versioning. The following image, from a Toptal blog by Konrad Gadzinowski (accessed January, 2024), illustrates the difference between the two approaches. While the Git Integration supports both, we recommend trunk-based development for SnapLogic assets. In the simpler trunk-based model, all branches are created from one master.

Comparison of trunk-based and gitflow development

The SnapLogic Git Integration currently supports the following Git platform providers:


  • Snap Pack and Snaplex assets cannot be tracked.
  • You can track only up to 1,000 assets per project.
  • Use authorized individual user accounts (not SnapLogic service accounts) to call any of the SnapLogic Git operation APIs.


  • Users must have read and write access to the appropriate Git organization, repositories, and SnapLogic projects.
  1. Configure your Git provider for use with SnapLogic Git Integration.
  2. Individual users must authorize SnapLogic to access their Git provider account.

Using the Git integration

Each organization has unique processes and requirements. While the SnapLogic Git Integration supports basic Git operations, it is important to understand how they relate to SnapLogic assets. The following pages describe: