Show HN: Ballet – Workflow automation that writes integrations against any API
1–10 of 21 posts
Re: Show HN: Ballet – Workflow automation that writes integrations against any API
#2Re: Show HN: Ballet – Workflow automation that writes integrations against any API
#3You drastically underestimate how bad most systems are. All of the vendors in your examples have good APIs. Those vendors already did the hard part.
All of the systems we need solutions for are moving targets that are breaking constantly. You can’t model those in 30 minutes because the ways in which they break don’t show up until months later.
Re: Show HN: Ballet – Workflow automation that writes integrations against any API
#4> We’ll model it in Ballet on your real systems in a 30-minute working session You drastically underestimate how bad most systems are. All of the vendors in your examples have good APIs. Those vendors already did the hard part. All of the systems we need solutions for are moving targets that are breaking constantly. You can’t model those in 30 minutes because the ways in which they break don’t show up until months la…
Re: Show HN: Ballet – Workflow automation that writes integrations against any API
#5- n8n
- tonnes of these keep popping up
Re: Show HN: Ballet – Workflow automation that writes integrations against any API
#6Perhaps I'm the wrong market for this project (despite much of my bread and butter being types of workflows) because I have no idea what Brainfish is.
Re: Show HN: Ballet – Workflow automation that writes integrations against any API
#7I think something like this could have worked several years ago but now it's overkill.
Re: Show HN: Ballet – Workflow automation that writes integrations against any API
#8The examples they show are someone typing something into a prompt and then some agent starts coding.
But the hard part in automation these days is not writing software. It is "how does the software get the credentials to access data and services? What APIs does it use?". So before being able to type a prompt and then use the software created, there must be the hard part: Setting up all those interconnectivity pieces. Making sure the software can access and change data, trigger actions, but only within a certain scope.