This creates a git backup of the workflows and credentials. It uses the n8n export command with git diff, so you can run as many times as you want, but only when there are changes they will create a commit. Setup You need some access to the server. Create a repository in some remote place to host your project, like Github, Gitlab, or your favorite private repo. Clone the repository in the server in a place that the n8n has access. In the example, it's the ., and the repository name is repo. Change it in the commands and in the workflow commands (you can set it as a variable in the wokflow). Checkout to another branch if you won't use the master one. cd . git clone repository Or you could git init and then add the remote (git remote add origin YOUR_REPO_URL), whatever pleases you more. As the server, check if everything is ok for beeing able to commit. Very likely you'll need to setup the user email and name. Try to create a commit, and push it to upstream, and everything you need (like config a user to comit) will appear in way. I strong suggest testing with exporting the commands to garantee it will work too.
Tags
Related workflows
See all General Automation→Tiny tiny Rss (aka tt-rss) Feed to Mastodon
Every 10 minutes look at your published news in your Tiny tiny RSS public feed and make a toot on your mastodon. You'll need: Your mastondon URL instance Your mastondon access token Your Tiny Tiny RSS public published feed URL
Automate Marker.io Issues to Intercom Conversations with Full Technical Context
Automatically create Intercom conversations with full technical context when your team receive new Marker.io issues 🎯 What this template does This workflow creates a seamless bridge between Marker.io and Intercom, your customer support platform. Every issue submitted through Marker.io's widget automatically becomes a trackable conversation in Intercom, complete with technical details and visual context. Centralizing customers issues in Intercom helps your support agents continue the conversation right where they work every day. When a bug is reported, the workflow: Creates or updates the reporter as an Intercom contact Opens a new conversation with the reporter and the all issue details Adds a comprehensive internal note with technical metadata Preserves all screenshots, browser info, and custom data ✨ Benefits Zero manual entry** - All bug details transfer automatically Instant visibility** - Support agents sees issues immediately Rich context** - Technical details preserved for developers Better collaboration** - Single source of truth for bugs Faster resolution** - No time wasted gathering information 💡 Use Cases Product Teams**: Streamline bug triage without switching tools S
Using the Merge Node - Merge by Key
This is an example of how you can make Merge by Key work. The “Data 1” and “Data 2” nodes simply provide mock data. You can replace them with your own data sources. Then the “Convert Data” nodes are important. They make sure that the different array items are actually different items in n8n. After that, you have then the merge with the merged data.