Version Control for Make.com Flows: Best Practices and Possibilities

Features
1

Hi Make.com Community,

I’m looking for a way to implement version control for my flows in Make.com. As my workflows grow more complex, it’s becoming increasingly important to track changes, revert to previous versions, and collaborate effectively. Unfortunately, I couldn’t find a built-in version control feature or clear guidance on this.

Here are my specific questions:

  1. Does Make.com have any built-in tools for version control (similar to Git or other versioning systems)?
  2. If not, how do you manage changes to your flows? Are there any best practices or workarounds you use for maintaining backups or tracking updates?
  3. Are there third-party integrations or tools you recommend for this purpose?

Any tips, tricks, or insights would be highly appreciated! I’d love to hear how others handle version control in their workflows.

Thank you in advance for your help! :blush:

2

@Kirill_Vodopianov
I don’t have a concrete solution, but I am interested in this topic too, so I comment on it.

  1. Does Make.com have any built-in tools for version control (similar to Git or other versioning systems)?

No, nothing.

  1. If not, how do you manage changes to your flows? Are there any best practices or workarounds you use for maintaining backups or tracking updates?
  2. Are there third-party integrations or tools you recommend for this purpose?

I have one idea, blueprint.json upload to Github by using Github actions and make. Then, i think that users are able to check what something is changed.

3 Likes
3

Hello @Kirill_Vodopianov

There is a way around with ncScale for free.

Please take a look at our cofounder Benoit’s post.

If you need any help, feel free to reach out to us.

3 Likes
4

Hello @biswa,
Thanks a lot for your answer.
I’ll definitely will take a look.
Regards,

5

Hello @biswa
Unfortunately, this feature is only available in the paid version, so I can’t test it to determine whether this solution is suitable for me.

6

I haven’t tested this, but I have a rudimentary hypothetical setup.

If the make.com “get a scenario blueprint” element is able to return an export of the scenario code as json, you could push it as a file using the Gitlab “Create A File In A Repository”, then use Gitlab for version control.

That said, there does seem to be some version control built in, where you can roll back up to 60 days.

You could also possibly just add a timestamp to the name and back them up to Google Drive.

1 Like