Looks like https://github.com/MoritzLaurer/GPT-google-sheets
Now this I would use…
Launch HN: Manaflow (YC S24) – Automate repetitive office work in tables
11–20 of 26 posts
Re: Launch HN: Manaflow (YC S24) – Automate repetitive office work in tables
#12Great job on putting stuff out there.
I understand the reasoning behind using spreadsheets, but wouldn't a flow chart/node based interface make more sense for this and be more intuitive? That way people can just upload their sheets/list to the beginning of the node and the subsequent actions/nodes would be the agents.
I have more comments/feedback if you're interested (mostly UX).
Re: Launch HN: Manaflow (YC S24) – Automate repetitive office work in tables
#13I looked at the video demo and tried the live demo and I still have no idea what it does and what value it brings to the user (why adding a watermark to a video needs an AI?). Also, it's super slow and not responsive. So many AI startups and I have yet to see one that makes sense for me. But I don't blindly trust any output from any LLM, so that's probably the reason.
Hi, thanks for trying out our demo! You're right - watermarking a video doesn't need AI, but we use AI to help enable nontechnical users to build that watermarking workflow, as well as any other workflow that they want to automate without having to interact directly with Python scripts.
[deleted]
Re: Launch HN: Manaflow (YC S24) – Automate repetitive office work in tables
#14Does this integrate with Google Sheets or Excel? If not, i would not use this. My workflow lives in spreadsheets but not your custom spreadsheets. They live in Google Sheets/Excel so you need to meet me where I do my work if you want to make my life easier
Yes, we have integrations with Google Sheets, so you can write directly there.
Re: Launch HN: Manaflow (YC S24) – Automate repetitive office work in tables
#15Re: Launch HN: Manaflow (YC S24) – Automate repetitive office work in tables
#16Another one of these companies which will sell to other YC companies and "exit" in a few years.
I wish you luck but honestly it seems like you have not done the ground work behind what operation managers actually do.
Re: Launch HN: Manaflow (YC S24) – Automate repetitive office work in tables
#17I tried to launch the demo, it's stuck in "Loading Manaflow demo...".
Console has errors:
> failed to load resource: the server responded with a status of 422 () clerk.browser.js:2 Uncaught (in promise) Error > at s._fetch (clerk.browser.js:2:48584) > at async X._baseMutate (clerk.browser.js:2:49256) ingest/static/recorder.jsv=1.139.3:1
> Failed to load resource: the server responded with a status of 404
Re: Launch HN: Manaflow (YC S24) – Automate repetitive office work in tables
#18[flagged]
Re: Launch HN: Manaflow (YC S24) – Automate repetitive office work in tables
#19[flagged]
Re: Launch HN: Manaflow (YC S24) – Automate repetitive office work in tables
#20If you're going to use a spreadsheet as your UI, I think you should be more careful how you describe the semantics of rows and columns. And make a strong case for why this representation makes sense. People expect that rows represent observations and columns represent variables. Along those lines, would it not be more accurate to say each row represents an instance of a task and column represents a sub-task or step i…
Seconding this -- I actually had copied "each column represents a step in the workflow and each row corresponds to an AI agent executing a task" to post a comment like this, but then checked through the comments to see if someone beat me to it, and here you are!
I'll add my terminology though, since it's slightly different. I think we're mostly agreed that "each column represents a step in the workflow" is fine. But for me the sheet represents an agent configuration, and each row is a specific job the agent performs.