This feature is available in our paid editions. Contact us here, and we'll be delighted to assist you!
The Git Sync feature allows for the creation of an external backup, environments, and maintaining a version history.
This example explains a simple setup for creating development and production environments. The setup can be extended to include multiple environments and multiple Git branches.
Requirements:
After making changes in the flow, You click on arrow near the flow name and select “Push to Git”, Add commit and puysh.
Please note that the credentials will not be synced automatically. You should manually create identical credentials with the same names in both environments.
You can trigger a pull from the Git Repository button in Activepieces. This action will replace all flows in the project with those from the git repository.
To manage your approval workflow, you can use Git by creating two branches: development and production. Then, you can use standard pull requests as the approval step.
This GitHub action can be used to automatically pull changes upon merging.
Don’t forget to replace INSTANCE_URL
and PROJECT_ID
, and add ACTIVEPIECES_API_KEY
to the secrets.
This feature is available in our paid editions. Contact us here, and we'll be delighted to assist you!
The Git Sync feature allows for the creation of an external backup, environments, and maintaining a version history.
This example explains a simple setup for creating development and production environments. The setup can be extended to include multiple environments and multiple Git branches.
Requirements:
After making changes in the flow, You click on arrow near the flow name and select “Push to Git”, Add commit and puysh.
Please note that the credentials will not be synced automatically. You should manually create identical credentials with the same names in both environments.
You can trigger a pull from the Git Repository button in Activepieces. This action will replace all flows in the project with those from the git repository.
To manage your approval workflow, you can use Git by creating two branches: development and production. Then, you can use standard pull requests as the approval step.
This GitHub action can be used to automatically pull changes upon merging.
Don’t forget to replace INSTANCE_URL
and PROJECT_ID
, and add ACTIVEPIECES_API_KEY
to the secrets.