Budibase introduces AI agents for operations teams. Handle requests, approvals, and workflows automatically - connected to your data and tools. Trigger from Slack/Teams/Discord, build apps when needed, and let agents do the work.
We’ve spent years helping teams build internal tools.
But we kept seeing the same thing:
Most operations work isn’t about apps.
It’s about handling requests.
Access requests. Approvals. Repetitive workflows.
The stuff that keeps teams busy.
So we started asking:
What if you didn’t build the workflow at all?
What if it just… ran?
That’s what led us to AI agents.
With Budibase, you can now:
• Handle requests automatically (from Slack, forms, etc.)
• Run approvals and workflows end-to-end
• Connect directly to your data and systems
• Build apps only when you actually need them
Instead of building tools, you define what should happen.
The agent handles the rest.
This feels like a new chapter for us.
Would love to hear what you think 🙌
Similar to how there could be internal tool sprawl, could there be an issue with AI agent sprawl? For instance, AI agents spun up that do very similar tasks being used within the same team when there should really only be one?
Open source AI agents for ops is an interesting wedge - the self-hosted angle matters a lot for anything touching customer data or internal workflows. Most teams I know are cautious about letting a SaaS agent touch their CRM or support queue. How does Budibase handle the agent permissions model - is it role-based on what the agent can read/write, or more of a "here is the whole app, go" setup?
“AI agents that run operations” sounds great. In reality, most workflows break on edge cases.
Joe Johnston