I’m sure that’s easy. There’s a bunch of services that use webhooks, email, slack etc. Unfortunately for an extremely simple dashboard to view responses and provides push notifications on mobile, I haven’t found any services. That’s I built a clean mobile app that provides push notifications. That way your email doesn’t get cluttered, you get notified, and you have a simple way to view responses without any setup.
It’s not for everyone, if you want to roll your own setup that’s great. But I intentionally built this for developers to give them full flexibility while still saving them time so they can focus on more important work.
What are the biggest issues that the agent faces at the moment? I still find these general purpose agents frustrating to use at times because people position it as if it could do anything and then when you give it a reasonably complex task it breaks down.
I guess if someone figured out way to minimize the impact of an error, like a way for it to gracefully handle it without it feeling like too much work, that would fix most of the problems.
That's great for most people. I wanted a little more - a notification on my phone when I got a submissions. Unfortunately setting this up is pretty annoying, and nobody else was doing it. They were only doing email and slack notifications which I didn't like as it just cluttered my inbox.
Forms are everywhere: contact forms, support forms, feedback forms, ...
For startups, it is important to monitor and quickly respond to events like sign ups or form submissions. This post explains the different options to handle form submissions without managing the backend yourself.
I think this is the more important question too. I don't think it is right in many cases to use the identity of the user and provide access to these agents. If it a simple one-time task, that might work if you can give restricted temporary access to the agent.
But for any other long-term task that may span hours or days while needing access to various data sources or APIs, we need a system where the agent has its own identity (which may be tied to the user). Just as humans are, agents might not function in the ideal manner at all times. So, we might need a system to monitor 'karma' of these agents. That ways API providers can confidently provide access to both humans and agents, and limit their risk to dangerous agents.
Yeah my initial reaction was not too positive. There's something weird to me about simply delegating verification to a third party organization. I'd prefer a more pure solution. Maybe we don't have a solution yet that is simple enough for widespread adoption. The domain based identity does seem a bit too complicated for the average user.
It’s not for everyone, if you want to roll your own setup that’s great. But I intentionally built this for developers to give them full flexibility while still saving them time so they can focus on more important work.