😱 << me screaming into the void What I thought was a “simple” workflow has turned into a soul-crushing labyrinth of despair 4 steps: Starting with a list of 15 LinkedIn post URLs in google sheets 1. Like each of the posts 2. Scrape the post's text 3. Send the text to chatGPT with a prompt to generate a comment 4. Post the comment to the original post Easy right??? WRONG! Spent 7 hours on this and it's still not working...and I'm a former systems engineer. I want to take a hot screwdriver and stab myself in the eyeballs. 😵‍💫 After wrestling with (and losing) a 2.5 year long battle with v1, I've determined that this isn't where I want to spend my time. I'm mentally bloodied, battered, and beaten 🤕....and don't have it in me to step into the ring with v2. 🥊 Maybe it's the app. 🤔 Maybe it's me. 🤷‍♂️ Maybe it’s karma from atrocities I committed in a past life. 😈 Regardless, my life would ascend to an unparalleled bliss, a utopia of peace and sanity, 😇 if I never have to dive into the soul-sucking abyss of figuring out Texau ever again. I just want to be able to tell someone what I want to do, they deal with all the skullduggery and it "magically" works...and makes me absurd amounts of money. 👉Can I hire someone to setup and run all my automations please? 🙏 Either reply or DM if you are open to being my Texau goto guru 🧘‍♂️

From the shock and awe show on Friday 10/4, I have the impression for some reason that n8n is a more powerful platform, or maybe that the Texau integration is tighter or more granular. I like the idea of using Open Source, but am mostly a no-coder.... Any suggestions on which platform to start with ?

I'm curious if anyone is still using Texau reliably. It seems like there's less activity here. I'm just wondering if people are still using it or have given up. I was a huge fan of V1, mainly because it didn't have updates! It's funny when you think about it. People complained about issues and the lack of new features, but it worked! Now, with V2, things break all the time. They fix one thing, and something else breaks. I'm starting to think that whoever is responsible for deploying code to production doesn't understand how B2B software releases work. Let me explain: when you have a product that companies (like us) use as a process, it takes time to train the team, create automation, and align it with other business processes. Then, when your junior developer releases an update that breaks our process, it's a huge pain. For example, they recently changed the Google Search Maps "Extractor," which was working fine, to a new version called Google Search Maps "Export." Which, by the way, it's still not working properly. Now I'm left with both versions not working and will probably have to edit hundreds of automations manually, one by one, because of this name change. Another time, there were similar unnecessary changes, like when they changed the header names of columns in the results. For example, "numberOfReviews" became "Reviews Count," not realizing that such changes break our integrations with other processes. These are just a few examples, but I could easily give 10 more. Guys, I understand you're just starting and trying to launch a real business. But if you want to build solid software for businesses, you need to understand and respect how your users use your product and how it impacts their needs. Please have a better QA review before releasing code. Recently, it got really bad. One last, very basic thing your team should know: I understand you value your weekends, Diwali, or whatever, but don't release new versions just before you leave the office! It's the other way around! You need to be around right after the new code is in production so you can address any issues if something breaks.