Ethan K. I just really dont want to go and learn another platform but at this point it makes it extremely hard to build agents for clients.
let me explain how we do this. our clients comm through private slack channels on our slack.
we add an app to the channel, so they can @xxxxxx the app, then in the flow we just name the trigger filter for the agent the same as that app, even though it doesnt pass anything through the app, it just makes it easier for them to understand how to use the agent.
we collaborate with them inside of slack with their team and get results directly from the agent, live and they can use as they see fit inside of that channel.
now you can understand why something like the authing issue not being super clear and easy to manage, causes a problem.
dumping the tools into an agent skill set along with a prompt is 1000x faster than building an entire workflow and it gives them additional freedom to ask the agent to do certain things. its created an extremely sticky offer for us because we can add another agent to their lindy for other tasking they need. it allows us to build their agents for them, and them not need to learn a platform, and we can work with them and troubleshoot live.
I have one lindy that has 4 different agents in it, that can handle almost ALL of my work flow and tasking.
i have clients that need this, but we want to roll it into the rest of our stack because of how sticky our offer is becuase of it.
