Urgent.News

What's breaking now, across thousands of outlets.

Monday, 19 October 2026 Reading Room

Tech

n8n-sync — Git-based version control for n8n Community Edition workflows

If you are self-hosting n8n Community Edition, you already know the pain: no built-in version control. Enterprise has Source Control at €667/mo, but for Community users, there is nothing. I got tired of manually exporting workflow JSON, committing it, and fixing credentials by hand when promoting from staging to production. So I built n8n-sync — a CLI that gives you Git-friendly version control…

dev.to ·

If you self-host n8n Community Edition, you're likely familiar with the lack of built-in version control. Enterprise users enjoy Source Control for €667/month, but Community users have no such option. Frustrated by manually exporting workflow JSON, committing it, and fixing credentials when promoting from staging to production, developer Badwal created n8n-sync, a CLI tool that provides Git-friendly version control for n8n workflows.

n8n-sync features include:

- Pull: Export all workflows to normalized JSON files for easy diffing

- Push: Create/Update workflows with credential mapping + dry-run

- Diff: Show semantic differences between local files and your instance

- Status: List all workflows with drift detection

Useful features include:

- Diff --check exits 1 on drift, perfect for CI pipelines

- Credential mapping between staging/production without manual fixes

- YAML frontmatter + sorted JSON makes Git diffs actually readable

- No n8n Enterprise required

To get started, run:

1. n8n-sync init

2. n8n-sync pull

3. n8n-sync diff --check

4. n8n-sync push --dry-run

5. n8n-sync push

n8n-sync eliminates the black box nature of self-hosted n8n workflows by treating them as first-class Git citizens. This gives you history of changes, ability to review workflow modifications before going live, CI/CD integration, credential management across instances, and rollback capabilities for broken workflows.

For more information, visit the repository at https://github.com/badwalx/n8n-sync. Share your feedback and let Badwal know what else would make this tool even more useful for your workflow.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

The Test Wasn't Wrong. It Was Answering an Older Question.

The Test Wasn't Wrong. It Was Answering an Older Question. I shipped a change I had reviewed, simulated, and deployed. An hour later my acceptance suite was red.

  • Test results were misinterpreted as code errors due to outdated data
  • Three categories of red results: missing artifact, stale expectation, genuine regression
  • Genuine regression poses most insidious issue by failing test expectations

·dev.to

WordPress Hooks Explained: How Plugins and Themes Extend Core Without Editing It

WordPress plugins and themes change what gets displayed and how data gets processed without ever touching WordPress core's own files (the code under wp-includes / wp-admin ).

  • WordPress plugins and themes use hooks to extend core functionality without altering source code.
  • Hooks come in two types: actions, for performing side effects, and filters, for altering data.

·dev.to

HELLO FRIENDS

I build crypto signal engines. My flagship system, USS (Unified Signal Scanner), combines momentum, multi-timeframe trend analysis, Smart Money Concepts, and dynamic risk management — 21 filters…

·dev.to

Quantified Self: How I Handled 100GB of Messy Biosensor Data with Polars and Dask

We live in the era of the "Quantified Self." Between my Oura ring, Apple Watch, and continuous glucose monitor (CGM), I’m generating more data than a mid-sized SaaS startup from 2010.

  • Process 100GB biosensor data using Polars Lazy API to avoid RAM overload
  • Align varying biosensor time series with Polars, resample, interpolate data
  • Scale processing with Dask and store results in efficient Parquet format

·dev.to

ARTF Explained: How a Live Bid Request Gets Patched Before the Auction

On 14 October 2026, Prebid previewed an auction model where ad servers bid into Prebid Server instead of the other way around ( AdExchanger ).

  • ARTF inverts traditional ad server-bidder process, with Prebid Server bidding first.
  • ARTF v1.0 framework introduces containerized agents to propose bid request modifications.
  • Agents can adjust deal floors, add metrics, and specify path/value changes in bid request.

·dev.to

More from Monday 19 October →