Approving an asset. Refreshing an SEO dashboard. Booking time on a round robin calendar. Two things all of these mini applications have in common. They require pulling or updating information from tools and they can be built in Gumloop with live artifacts.
Now live artifacts are simple. It means the artifacts you build on Gumloop can interact with the data they’re built on top of. They’re no longer static. They actually feel more like mini applications.
Let’s take this Google Sheet of an upcoming event, a very exclusive one, and I want to make it easy for anyone on the team to approve guests. So I’ve got this Gumloop agent with access to Google Sheets, Slack, and Apollo and I want to create an app where anyone on the team can come in and approve outstanding guests.
Now let’s go to the agent and type: “Create an app where we see stats about our event and a list of guests that need approval, and when I approve a guest I want the sheet column ‘approved’ to be updated to yes and a Slack message sent to the events channel letting the team know that we’ve approved a new guest.”
Very cool. Now I’m going to let the agent cook here and what’s happening is that the agent is writing an application. It’s building the UI that our team will interface with, connected to the back end of our application. In this case it’s going to be our Google Sheet, but it can be anything you use.
Now let’s see what it came up with. That’s pretty cool. We have a live artifact, basically an application. We can approve outstanding attendees and see that it updates the underlying sheet and sends a Slack message just like we want. We can refresh to see any updates in the sheet reflected here as well. And just like that we’ve built an app, a live artifact.
Now the final note here is that these artifacts are no different than regular artifacts in that you can share them with a colleague, a team, or an organization. The main difference is that because this is pulling and acting on real data, we’ll always make sure that the person interacting with this artifact has access to the underlying tools. If they don’t, they won’t be able to see or update the information.
And that’s it. Go make that booking app, that approval workflow, the interactive seating chart that you’ve always wanted to build, all within Gumloop.
Live Artifacts
Live artifacts turn your agent’s output into interactive mini applications that read and write real data from your connected tools.
Artifacts in Gumloop used to be static. Your agent could generate a dashboard, a report, or a table, but it was a snapshot. Live artifacts change that. They stay connected to the tools they were built on, so the data is always current and users can take action directly from the artifact itself.
What makes an artifact “live”
A live artifact can pull fresh data from your connected tools and push updates back. Instead of viewing a frozen table of event guests, you get an app where you can approve a guest, and that approval writes back to your Google Sheet and fires off a Slack notification. The artifact becomes the interface for the workflow, not just a readout of it.
Building one
You describe what you want in plain language. Tell your agent which tools to connect, what data to display, and what actions should happen when a user interacts with the artifact. The agent handles the UI and the backend wiring.
In the example from the video, a single prompt produced a guest approval app that:
- Showed event stats and a list of guests pending approval
- Updated the “approved” column in Google Sheets when a guest was approved
- Sent a Slack message to the events channel on each approval
- Reflected sheet changes on refresh
The data source was Google Sheets, but it could be any tool your agent has access to.
Sharing and permissions
Live artifacts can be shared just like static ones, with a colleague, a team, or an entire organization. The difference is that because a live artifact reads and writes real data, Gumloop checks that the person using it has access to the underlying tools. If they don’t, they won’t see or modify the data. This keeps things secure without requiring you to manage access separately.
What to remember
Live artifacts work best for repeatable, interactive workflows. Approval queues, dashboards that need fresh data, booking tools, anything where your team needs to act on information rather than just read it. Describe what you want, connect the right tools, and let your agent build the app.
