Blog
Things we ran into at work and could not find in the documentation. Mostly n8n, CRM and integrations.
Duplicates in the CRM: how to merge contacts and deals without losing anything
The same customer is in the database twice — as two contacts and as two deals. The manager sees half the history, the report counts two people, and the built-in merge folds the fields together and can lose the rest.
The customer identifier: why it has to be the email
One buyer turns into three in the report. Not because the database has duplicates, but because the query groups people by fields they fill in differently every time.
Subscriber growth: why the obvious count overstates it
You compare list sizes at the start and the end of the month and see growth. In fact half of those people were with you last year — they were simply moved into a different list.
How to keep n8n workflows in code: a generator instead of clicks in the editor
Six months on, nobody remembers why a node is set up the way it is, and the copies of one workflow across different accounts have already drifted apart. The editor is no help here.
An ad dashboard in Google Sheets: when it stops working
Pulling three ad accounts into one spreadsheet is the obvious answer, and it works right up until the data gets big. After that it breaks the same way every time.
How to recover data that was bulk-deleted in a CRM
Somebody ran a bulk operation on the wrong segment, and tags, links or whole records vanished from the list. There is no undo button. But in most cases the data is still there.
Schedule Trigger in n8n: why the schedule stops firing after an update
You pushed a new version of the workflow through the public API, it is active, there are no errors — and the Schedule Trigger never fires.
Describe your situation
Tell us which process eats the most time. We will write back with what can be automated and roughly what it would cost.
Discuss a project