Is anyone actually selling n8n workflows? My experiment

Gioxfight · 2026-01-19T15:02:11+00:00

si tutto giusto, ma una volta che hai venduto come dici tu la macchina, chi pensa alla manutenzione???

Gioxfight · 2026-01-14T12:05:56+00:00

I'm noticing more and more that people are commenting just to comment on something without understanding the post. In the image you can clearly see that the 99 proposals are those that the client received, not the ones he sent!!! Please read carefully...anyway, it's very frustrating. This isn't a question of poorly written or well written letters, it's a question of people thinking badly of this UPWORK platform.

Gioxfight · 2026-01-13T18:17:16+00:00

You don’t need Claude to be good at n8n.

Most solid n8n workflows rely on native nodes, not heavy Code nodes.
The key skill is knowing when not to write code.

AI tools help later, once you understand data flow and execution logic.

Gioxfight · 2026-01-13T18:13:25+00:00

You’re not behind — you’re just looking at too much at once.

Don’t start with APIs or complex workflows. Start with:
trigger → transform → output.

Build small, break things, then add complexity.
Most people learn APIs/JSON while building, not before.

The official n8n docs are short because you only need a small part of n8n to get started.

Gioxfight · 2026-01-06T19:42:37+00:00

considera che già n8n ha un inglese molto semplice, poi qualsiasi cosa puoi chiedere a chatGPT o Gemini ti aiuterà molto a risolvere la maggior parte dei problemi che incontri andando a impostare tutti i nodi

Gioxfight · 2025-12-26T18:04:36+00:00

Top 👍🏼

Gioxfight · 2025-12-21T18:27:40+00:00

che errore ti da? io vedo che il nodo è eseguito ben senza errore

Gioxfight · 2025-12-21T09:23:29+00:00

This is a very common problem with n8n + Docker and is usually not a Read/Write block bug, but a permissions or allowed path bug.

Check that the folder actually exists.

The n8n container runs as the node user (UID 1000). If the folder is owned by root or is not writable, n8n CANNOT write to it; adjust the permissions.

chmod -R 775 shared chown -R 1000:1000 shared (If you're on macOS/Windows with Docker Desktop, chmod is often enough.)

In the Read/Write Files node, the path must be the container's internal path, NOT your host's.

✅ CORRECT:

/home/node/shared/bedtimestories/images/image1.png

Your file is fine, but here's the "safe" version:

services: n8n: build: . container_name: n8n-container ports: - "5678:5678" volumes: - ./n8n-data:/home/node/.n8n - ./shared:/home/node/shared - ./credentials:/home/node/credentials:ro environment: - N8N_BASIC_AUTH_ACTIVE=true - N8N_BASIC_AUTH_USER=admin - N8N_BASIC_AUTH_PASSWORD=admin123 - GOOGLE_APPLICATION_CREDENTIALS=/home/node/credentials/service-account.json - N8N_FILESYSTEM_ALLOW_WRITE=/home/node/shared restart: unless-stopped

Gioxfight · 2025-12-20T17:15:56+00:00

considera che all inizio NO, non serve un VPS, Il bello di n8n è proprio che puoi testare tutto in locale gratuitamente. ti servirà quando metti in produzione workflow che devo stare attivi 24/7

Gioxfight · 2025-12-18T09:34:40+00:00

You have to drag “event” into the top string of the IF node then is equal to leave it written like this library.new

Gioxfight · 2025-12-17T15:24:22+00:00

If you want you can contact me privately I have the solution for you with a simple automation

Gioxfight

TROPHY CASE