How are you protecting against Willison's lethal trifecta attacks in agents connected to tools like shown here - https://tramlines.io/blog
101008 60 minutes ago [-]
I want to create something that every X hours (could be 6 hours, 8 hours, 12 hours) check if there are news about a certain topic, and if there are and are interesting enough, generate an image, a text, and post it to Instagram.
The second part is done (generating it and posting it), but finding the news is the hardest part, even if I share some RSS feed. Would this help me with my use case or is something completely different?
segmenta 42 minutes ago [-]
This is great, and exactly the type of thing we would love folks to build on Rowboat!
Rowboat has tools to search the web, find HN posts, browse Reddit etc, and you can ask the copilot to build an agent to filter posts based on topics - at the granularity that you want. We have time based triggers, so you can have the agent invoked every x hours.
I tried using your cloud solution to test this and I couldnt pass the connect to Instagram through Composio. I got a 400 error. I checked Reddit and it never worked. Got tired after trying for a while :(
Google used to have news alerts. Have you checked those?
one_d4 45 minutes ago [-]
I did that using n8n. Quite easy to setup a workflow that reads an RSS feed. Maybe give it a try.
segmenta 16 minutes ago [-]
Would love to know how you find Rowboat for this!
warthog 48 minutes ago [-]
What is the core use case here? For example instead of adopting a dedicated customer support chatbot, why should someone build one on Rowboat? As far as I can see, the customisability parameters are not that different
segmenta 23 minutes ago [-]
Great question. Rowboat is a non-opinionated agent framework, so you can build support bots but also meeting prep, reporting, repo management, and other daily automations in the same place.
Even for support, it's more flexible: companies are shifting from narrow "customer support" to broader customer experience - not just resolving tickets, but handling onboarding, account health, proactive updates, and escalations across teams. With Rowboat, you can compose cross-functional agents across support, product, and ops. The same system that answers tickets can also trigger workflows, update dashboards, or prep reports.
Does this make sense?
ActionHank 1 hours ago [-]
Who is your ideal customer and what could they create?
What is the plan if, like Jetbrains have recently experienced, customer usage exceeds the $20?
akhisud 49 minutes ago [-]
Our ideal users are developers and product teams who want to automate everyday workflows for themselves and their users. Examples include meeting prep, daily/weekly reporting, project management, GitHub repo management, and customer support.
Power users treat Rowboat as their daily go-to assistant for a range of different tasks, customizing assistants for themselves and expanding to cover more use cases.
Regarding pricing: If usage exceeds beyond the $20 (starter) plan, we have a $200 (pro) plan that users can upgrade to. Additionally, we will soon be launching pay-as-you-go pricing as well.
asdev 1 hours ago [-]
why would I use this over n8n?
akhisud 1 hours ago [-]
From our experience, n8n is great for linear workflows and connecting APIs through flowcharts. Rowboat is aimed at building agentic systems (multiple orchestration patterns, autonomous agents coordinating, non-linear decision making).
Those are much harder and time-taking to express and maintain in a flowchart model. Our goal with Rowboat was to make it simple and quick to build and maintain multi-agent assistants. Hence, the copilot is equipped with tools and state-of-art orchestration patterns [1], which allow it to build ready-to-go assistants in minutes from high-level requirements.
Looks very similar to relevance ai. How should we think about this product’s difference other than oss
akhisud 1 hours ago [-]
Thanks for the pointer! We briefly checked them out. Looks like they use a flowchart-style canvas - that’s great for certain types of automations.
Rowboat is especially designed for agentic patterns (e.g. manager-worker) which lend more autonomy to agents. Rowboat's copilot is empowered to organize and orchestrate agents flexibly, based on the nature of the assistant.
The second part is done (generating it and posting it), but finding the news is the hardest part, even if I share some RSS feed. Would this help me with my use case or is something completely different?
Rowboat has tools to search the web, find HN posts, browse Reddit etc, and you can ask the copilot to build an agent to filter posts based on topics - at the granularity that you want. We have time based triggers, so you can have the agent invoked every x hours.
We have a similar prebuilt template you could checkout: https://app.rowboatlabs.com/projects?shared=N2pJTzyTdh-NdwMi....
Even for support, it's more flexible: companies are shifting from narrow "customer support" to broader customer experience - not just resolving tickets, but handling onboarding, account health, proactive updates, and escalations across teams. With Rowboat, you can compose cross-functional agents across support, product, and ops. The same system that answers tickets can also trigger workflows, update dashboards, or prep reports.
Does this make sense?
What is the plan if, like Jetbrains have recently experienced, customer usage exceeds the $20?
Power users treat Rowboat as their daily go-to assistant for a range of different tasks, customizing assistants for themselves and expanding to cover more use cases.
Regarding pricing: If usage exceeds beyond the $20 (starter) plan, we have a $200 (pro) plan that users can upgrade to. Additionally, we will soon be launching pay-as-you-go pricing as well.
Those are much harder and time-taking to express and maintain in a flowchart model. Our goal with Rowboat was to make it simple and quick to build and maintain multi-agent assistants. Hence, the copilot is equipped with tools and state-of-art orchestration patterns [1], which allow it to build ready-to-go assistants in minutes from high-level requirements.
[1] https://cdn.openai.com/business-guides-and-resources/a-pract...
Rowboat is especially designed for agentic patterns (e.g. manager-worker) which lend more autonomy to agents. Rowboat's copilot is empowered to organize and orchestrate agents flexibly, based on the nature of the assistant.