Activity
Mon
Wed
Fri
Sun
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
What is this?
Less
More

Memberships

Automate Business AI

4.8k members • Free

No-Code Nation

3.1k members • Free

Podcast Profits

913 members • Free

Tinocode

1.9k members • Free

SW Automation

6.5k members • Free

The RoboNuggets Network (free)

26.4k members • Free

AI Automation Mastery

22.5k members • Free

Brendan's AI Community

22.4k members • Free

AI Automation Agency Ninjas

19.2k members • Free

10 contributions to AI Automation Society
n8n Freelancers: Do you deliver JSON workflows or build directly in client’s n8n?
Hey everyone 👋Quick question for people freelancing with n8n. When delivering client work, what’s your standard delivery approach? - Do you usually build directly inside the client’s n8n instance (credentials, env vars, testing included)? - Or do you export and send the workflow JSON for the client to import? - Or a hybrid approach (core logic as JSON + setup guidance)? I’m trying to standardize my delivery process for Upwork/client projects and want to balance: - Professionalism - Client convenience - Protecting reusable workflow logic Would love to hear: - What clients expect in your experience - What caused problems (import issues, reuse, scope creep) - What you now do as a “default best practice” Thanks 🙏
0 likes • 14d
Mainly prefer to build everything out in client accounts. It minimizes buyer's remorse, as it gives the client full control of everything (ownership). However, I've had cases where the client doesn't want to share credentials - then I make sure the implementation of the JSON blueprint I build out on my own accounts is as straight-forward to them as possible. I guess my goal/approach to this is to maximize the deliverable, so the client feels like he's getting as much bang-for-buck as possible.
1 like • 14d
@Katherine Pacheco It depends. Usually the clients who don't want to give their n8n away have no issue giving away credentials/API keys to other tools for some reason. If that's not the case and they are very strict about just getting the JSON and authorizing themselves then yes, I will do my own softwares, but that usually doesn't happen on very complex projects where there are a ton of softwares - the ones I have to use my own are usually the basics like OpenAI, Google Sheets etc.
One n8n Account per Client — Is That Overkill or Best Practice?
When you make ai agents for clients do you open n8n account specifically for their workflows or do you have 1 account in which you have all the workflows created for each business specifically
1 like • 14d
If you're keeping the account, definitely all of the workflows on your own account, then send the JSON to the client. But I prefer building straight inside the client's n8n.
Scraping Leads
Okay I have rewritten this post - Ill keep it very short can anyone PLS show me exactly how you scrape a 1000 leads for free because I dont think its possible for free it must be on some paid plan of some sort, I am now on Apify and Apollo and if I dont get Germany when I ask for NZ, or if I dont get 46 when it found 887 or what ever I DO NOT GET A 1000 LEADS - PLS SHOW ME 🙏
0 likes • 14d
So you're saying the problem is Apify, not the direct lead source like Sales Nav/Apollo?
Improve Any AI Workflow
The Easiest Way to Improve Any AI Workflow Add one step: “Explain your reasoning briefly before answering.” Not for you — for the system. This helps: catch hallucinations spot bad assumptions debug broken logic If the reasoning looks wrong, the output usually is. -->Any suggestions you use in your own work? Already know about this? Any more specific information you know to make workflow better? How you design your workflows?
Improve Any AI Workflow
2 likes • 14d
Nice one. 💯
1-10 of 10
Karlis Leilands
3
38points to level up
@karlis-leilands-1316
Up and coming automation guy!

Active 10d ago
Joined Aug 5, 2025
Powered by