Dmytro Galko · open-source tools

automation-pipelines

Name: automation-pipelines
Author: Dmytro Galko

n8n owns the plumbing, Python owns the logic

This is the shape of most “connect these tools and stop doing it by hand” jobs. A webhook arrives, Python cleans, validates, scores and de-duplicates the payload, then it is written to a sheet and announced in Slack; a second module reads a PDF and decides whether it can be auto-approved or has to go to a human. The split matters: the logic that would be painful inside a no-code node lives where it can be tested.

Source on GitHub Work with me

What it does

Cleaning is where the money is: a mistyped domain, a phone in four formats and the same person submitting twice are the normal case, not the edge case.
Nothing is auto-approved on a guess — a document missing a field it needs goes to a person, with the reason attached.
The Python half has its own suite, which is the half a no-code canvas cannot give you.

How it is proved

47 tests pass on a clean machine, covering cleaning, scoring, the extractor and the HTTP surface.

Pythonn8n47 testsGoogle Sheets and Slack

People find this looking for

n8n python webhook pipeline, lead cleaning scoring dedupe, document field extraction auto approval, n8n google sheets slack automation.

If that is your week and you would rather someone else did it, write to hello@dkautomation.dev or open an issue.