@Chris Wong yeah should work. Or connect n8n to UI with webhooks, use supabase for auth directly in the application. No need to auth for the workflow itself I think. Workflow in the backend Set up DB if they need to store data. Done

@Chris Wong ;)

I have built a quiet complex one myself and found these points to be important: - Learn about Item pairing/linking/pairedItem: Its an extremely important concept to understand because many workflows that handle multiple data pieces per item (company details) error because of pairedItem errors and at first you have no idea why - Limit batch sizes for testing to save time: For testing, reduce batch size (limit node) and pin data whenever you can - Reduce token costs whenever possible: Dont let AI do tasks that can be done with a code node or another node that doesnt require tokens. - Use loops to reduce possible errors and make the process easier to oversee. Its easier then to find the cause of the workflow stopping without errors. - Send to relevant companies only to avoid blacklisting and getting marked as spam. - Consider setting up a lot of email accounts (20-40) and spread out the emails on all these adresses to reduce risk of getting marked as spam. - Keep the email short 60-150 words, use social proof. Offer something very easy at the start with as little "friction" as possible to make saying yes easier. Instead of "meet in person for one hour" say "discuss X for 15 min within the next two weeks" - Find a way to incorporate urgency when the offer is good - Change the email style, offer for every 100-300 emails to split test. You can also think about incorporating this in your workflow to automatically change the email style with the same input once 300 emails have been created I am also building a UI to make a propper app out of it so that I input a list and it gives me the list back with all the emails ready to be sent off.

@Rikhil Bollu ;)

May not sound too lightweight but have you thought about building your own with Lovable and n8n? It might be surprisingly easy, depending on the kind of data and processes it undergoes

@Bobby Kershaw Am building a tax app and built a validator screen to incorporate in a workflow (not done yet). Its very smooth but here and there I jump in and do some coding

think about what kind of clients you want to have first. 1. Many clients with low budget or 2. Few clients with a big budget. For 1. you can identify what most of them need and copy paste sell the solution to multiple of them with little changing for each client required ( keep that in mind while building ). For 2 you hook them with a smaller project that helps them do something easy with little investment. Once it works offer more and more tools to them.

@Daniel Yanchev 1. - you learn while building simpler automations which then also serve as the foot in the door for the clients in 2. Always make it a goal to earn something valuable (not necessarily money) ASAP while still learning. A simple project for free earns trust and a good review + potential referrals/connections.