Skip to main content
Ask your agent for a dashboard and it builds you a page: the numbers, charts, and tables you asked for, in a browser tab you can send to someone else. The same request also produces reports and maps. You don’t switch this on. When your request is better answered by a page than by a chat message, your agent builds one.
A dashboard page with headline figures across the top and charts and a table beneath them

A dashboard your agent built, open on its own page

​
Before you start

Your agent can only chart data it can reach. Give it a source first: an integration, knowledge you uploaded, or figures you paste straight into the chat.

​
Ask for one

Describe the result and who it is for. Your agent chooses the layout.
  • “Build me a dashboard of this quarter’s pipeline, broken down by owner.”
  • “Turn last month’s support tickets into a one-page report for the team meeting.”
  • “Put our office locations on a map I can send to a new starter.”
If the first version isn’t right, say so in the chat and your agent builds it again. When it’s ready, your agent posts a card in the chat — click Open page.

​
What a dashboard can do

Filters are the ones worth asking for by name. The page carries its own code, so a filter, a toggle between two views, or a search box over a long table keeps working for everyone you send the page to — no account and no set-up on their side. That turns a dashboard from something people look at into something they can ask their own follow-up question of.

​
Ask for a button that runs an agent

A dashboard can carry an action: a button a reader presses to ask one of your agents to do some work. A “Refresh report” button that rebuilds the figures is the common case, but it can be any request you would otherwise type into a chat.
Diagram: a dashboard with a Refresh report button hands a request to the agent behind it, which runs with its own instructions, integrations, and credits, and then rebuilds the page or files the workDiagram: a dashboard with a Refresh report button hands a request to the agent behind it, which runs with its own instructions, integrations, and credits, and then rebuilds the page or files the work

A reader presses the button, and the agent behind the dashboard picks up the work.

Ask for it explicitly, and name the agent that should do the work:
  • “Add a Refresh report button to this dashboard that asks my Pipeline Reporter agent to rebuild it.”
  • “Put a Refresh button on this dashboard that asks you to rebuild it.”
Your agent adds an action only when you ask for one in those terms. Asking for a dashboard, or for filters and other controls, never gets you one on its own. The agent you name can be the one that built the dashboard. For a refresh button that’s usually what you want: the agent that made the page is the one that can make it again.
Diagram: a loop between a dashboard and the agent that built it, where you press the button on the page and the same agent rebuilds that pageDiagram: a loop between a dashboard and the agent that built it, where you press the button on the page and the same agent rebuilds that page

A refresh button sends the work straight back to the agent that built the page.

​
What to use a button for

Each button sends your agent a message. Most of the time that message is fixed: you say what it should be when you ask for the button, and every press sends the same request. It can also be built from the page, so the agent hears which filter is selected, which row was picked, or what someone typed in. A box to type into is optional — plenty of useful buttons don’t need one. What a button can achieve depends on the agent you name. It’s a way to ask, not a new set of powers: if that agent can’t reach your tracker, a button won’t file the ticket. Only people who manage the agent behind the dashboard can use it. Sharing the page doesn’t share the action: Can view access, Anyone with the link, and use-only access to the agent are all deliberately not enough. Everyone else still gets the page, the figures, and the filters, but the button won’t start anything for them. So a dashboard isn’t the way to collect reports from a whole company — most of the people you want to hear from can’t press the button. Keep actions for a team that already manages the agent. For buttons that everyone you share with can press, build an app instead. The run starts straight away. There’s no second confirmation step, so ask for a button label that says plainly what pressing it will do. The agent you named then runs the way it always does, with its own instructions, its own integrations, and its own credits.
The button confirms that your request was sent, not that the work is finished. If you asked for a rebuild, give the agent time and then reload the page — the same address shows the new version. Your agent may also stop and ask for more information. The dashboard can’t answer that, so open the agent in Dataleap and carry on the conversation there. If you want a short answer back on the page rather than just a confirmation, ask for that when you ask for the button.

​
What it can’t do

A dashboard is a snapshot. It holds the data your agent had at the moment it built the page. It doesn’t refresh on its own, and the page itself can’t reach your integrations while you’re looking at it. For current figures, ask your agent again, add a button that runs the agent for you, or put the request on a trigger so it rebuilds on a schedule. If people should always see current figures, build an app instead.
The page itself still stores nothing and sends nothing. There’s no database behind a dashboard, so whatever someone types into it is gone when they reload, and the page makes no network calls of its own. An action doesn’t change that. It hands the request to an agent, and the agent is what saves it, files it, or writes it into a tool you’ve connected. If what people type in should be saved, build an app: it saves entries in the agent’s database.

​
Share your dashboard

Sharing a dashboard shares the page, not the agent behind it. People who open it see the result and nothing else: not your instructions, not your integrations, not the chat it came from. Open the dashboard and click Share in its header.
The share dialog for a dashboard, showing who currently has access and the general access setting

Choose who can open the page, then copy the link

To invite named people, type into the people field and leave the role as Can view — the only role a dashboard has. You can add a whole team or your organization the same way. Under General access, pick one: Then click Copy link and send it. A dashboard page keeps one address. Ask your agent to rebuild it and that same address shows the new version, so save the link once and it always opens the current dashboard. A link you sent last month shows this month’s figures, and nobody needs a second one. Who you shared it with carries over. The people, teams, and organizations you invited, and your General access choice, belong to the page rather than to one version. Rebuild the dashboard and they keep the access you gave them. Everyone holding the link sees the new version too. If a set of figures has to stay exactly as it was, ask for a separate dashboard rather than rebuilding over that one.
There’s no library of dashboards to browse. The link is how you get back to a page, so keep it.

Build an app

When the page should stay current, save what people enter, or have buttons everyone can press.

When to share what

Pick between sharing a dashboard, a template, and the agent itself.

Triggers

Run the request on a schedule so the dashboard rebuilds itself.