Welcome to the n8n section of the oTTomator Think Tank

Hey everyone!

Since I announced this part of the oTTomator Think Tank in my Flowise + n8n video today (teaser for those of you seeing this before 7:00 PM CST tonight haha), I wanted to make an introductory post to get this started!

This area of the Think Tank is for us to chat about everything n8n - creating agent workflows, sharing workflows you’ve built, troubleshooting app integrations, etc.

I truly believe open source is the future of AI, so open source tools like n8n that you can host yourself, use really easily to create local AI agents, and build local tools for your agents are really going to continue to shine more and more!

This area of our Think Tank is just getting started - so I’d appreciate you posting anything to help us get the ball rolling! Feel free to share workflows you’ve built with n8n (bonus if it is n8n + Flowise!), questions you have around n8n (I’ll personally answer them!), or anything you want!

10 Likes

Nice. I have a lot of thoughts around some similar tools and glad to see this section pop up :raised_hands:

1 Like

is there a way to turn the n8n AI RAG Agent to an API? so instead of a frontend, its a backend via api?

Yes you sure can!

I do that in this video:

4 Likes

can I somehow make this workflow work as it supposed to?

1 Like

Hey @eng.menamedhat! I would make this a separate topic in the n8n category and give some more details on what you are trying to accomplish and what your error is!

1 Like

n8n would cost €20 per month?: n8n Plans and Pricing - n8n.io

1 Like

I got a deal for a VPS with OVH that I’m paying $0.97/mo (for first year), but I believe it was a Cyber Monday thing. Packs enough performance for what I need and was simple enough to setup (but the low tier only gives you SSH).

On a side note, n8n really just a visual tool; you can do the same thing in pure code… so I wonder if there’s something to compile a workflow down to pure code and just use as a runner, action, or lightweight code on a webserver… then it would be great as more of development tool and just publish your workflow to production. Then it also doesn’t have to be “always on” and you can just spin it up locally as needed. Just something I’ve been thinking about.

1 Like