Grok Bot Pages: 4 Real Examples of What You Can Build

0:00This page on screen shows me an estimate of what my coding bot has cost me so far. I didn't have to build a spreadsheet or copy a single number into it. I just asked my bot in Grokbot to build it. Grokbot has just launched pages and they're more than just documents. Your bot can pull data from your connected tools, do the analysis, and turn it into something you can click, filter, and explore. And when you want fresh data, you can simply ask your bot to update the page or you can set a routine so that it updates automatically on a schedule. I've built three practical pages in my own setup plus a

0:28bonus one at the end that I think is the coolest. Let's jump in and have a look at Grokbot's new pages feature. So, here we are in Grokbot and I've got my scratchpad conversation open. This is the main entry point I use when I'm building things in Grokbot. What you can do here is just jump in and say, "I want to build a page. Give me some examples or use cases." What I did at the start was I said, "Analyze my entire Grokbot system and suggest some potential uses where pages would be valuable." It came back with a few ideas and now we've got to these four examples that I'll run

0:58through in this video. Once you've created a page, you can open it directly from the conversation and if you want to change something, you can just ask your bot. You can also share pages with your team or make them accessible through a link. Rather than just talking about the features though, let's go through a few

1:11examples of how I'm actually using them. So, the first page is a dashboard I created for managing my Snappa AI projects. If I click on the link here in this chat, that's going to open up the page. I've already got a project plan in Notion where I track everything I'm working on, but I wanted a simpler way to see what's happening across all of those projects. So, I asked my bot to pull that information together into a

1:31page that gives me a quick overview. That way, I can quickly open this up within Grokbot and get an idea of where I'm needed and where all tasks are sitting without having to jump into Notion or prompt Grokbot to tell me where I'm needed. And if we start here, I've got a list of things that need my attention on the left-hand side like reviewing a newsletter, approving website updates, and making decisions on upcoming work. And on the right-hand side, you can see I've got a list of upcoming tasks this week and next. Then further down it's broken out everything into four areas, my website, my bot

2:01team, content, and my newsletter. I can see the status of each project, how many open items there are, and what's currently happening. And these link back to the original project information in Notion, so I can jump straight into the details when I need to. I've also got a timeline of upcoming dates and milestones at the bottom. So rather than digging through my entire project plan, I've now got everything I need in one place in this page. Now, in this next example, it's a bit more interesting because instead of Notion, my bot is actually reading data from its own computer. Let's jump over and have a look at that one. So this

2:31page on screen is the one I briefly showed you at the start of the video. It's the Codex coding bot spend tally. If you've watched my previous videos, you'll know I've got a coding bot that uses Codex to make changes to my website and execute other coding tasks. And because Codex runs on Grokbot's own computer, I wanted to see how much it was actually costing me to use. And for that reason, Grokbot can access the runs and the coding projects that I assign to it and generate this estimate using that data. So there are a few reasons why I use Codex via Grokbot's personal computer. One is that I want to control

3:03my usage limits on Grokbot. I use it a lot for managing projects and coding tasks would also chew up some of that usage, so offloading that to Codex via that personal computer helps save on usage. It also allows me to track the costs as you can see here. So if I'm working on client projects, I want to see exactly how much I'm spending on coding tasks that I'm doing through Codex, I can see that exactly here. So I asked my bot to go through its Codex session logs, analyze the token usage, calculate the estimated API costs, and put everything into a dashboard. And here's what it

3:36came back with. It's got my estimated spend for the month, how many Codex runs it's completed, and the average cost per run. I've also set a monthly spending limit of $50 with an alert threshold at $25, so I can see how much of that budget I've used in real time. Further down it's created this chart showing me the estimated costs that have accumulated over time. I've got a breakdown of the individual runs as well, including when they happened, the

3:59token usage, and their estimated costs. So, I can also sort through the results to see which runs were the most expensive. And right at the bottom, it's included the pricing assumptions as well. So, at the moment, it's an estimate based on the token costs. What you can also do is set up an API key directly with GrokBot as well, so that it can access OpenAI and give you the exact costs. For this demo, I've just asked it to do an estimate, so it's pretty close to the actual number. So, it's good enough for what I'm currently using it for. That's an example of how you can use the data that you have

4:32within GrokBot to build a dashboard that gives you real-time data that you can use to make decisions. Now, let's have a look at another example, this time pulling information directly from one of my connected apps. Okay, so here is the next page on screen, and this page is connected to Kit, which is the platform I use to manage my Snappa AI email

4:48newsletter. I asked my bot to pull together the performance of my previous newsletters and create a dashboard showing things like open rates, click rates, subscriber growth, and which topics have been performing the best. And as you can see, I've got all my key metrics up here, including how my subscriber list has been growing and my average open and

5:04click rates. Further down, I've got this chart showing the performance of each newsletter over time. And I can actually interact with the data. For example, I can toggle resends on and off to see how those campaigns performed as well. I've also got a table of all of my broadcasts, which I can sort by things like open rates, click rates, or filter by different topics. This is probably one of the more interesting parts. You can see here the bot has grouped my newsletters into different topics based on their subject lines, so I can compare which types of content are getting the most engagement. For example, my Power D

5:34templates and model comparison emails have been performing really well for clicks. As we scroll down, you can also see it's got best subject lines by open rate and click rate that I can sort through, and also the topic. And then we've got recommendations here for what I could try next, things like bringing back downloadable templates and focusing on content with a clear comparison or result. Obviously, these are suggestions I'd still want to test, but it's useful having the analysis done for me. And

5:59that's what I like about this example. I'm not just looking at the numbers from Kit. I've asked my bot to organize the information, analyze it, and build a dashboard around the questions I actually want answered. Now, this one, page left, let's jump into that and have a look now. And finally, we have this Meet the Bot Team page, which shows an overview of my entire GrokBot system. I asked my bot to create an interactive map of my entire GrokBot team showing how the different bots work together and hand off tasks to each other. So, I've got everything broken down into three areas, website, content and audience,

6:28and operations. And these arrows show how work moves between the different bots, including the points where something needs my approval before it can move forward. But what's really cool is it isn't just a static diagram. I can actually click on any of these bots, and down at the bottom here will show me the description of the bot and its job and what rules it follows. So, you can see if I click on website Pam, for example, the

6:49description at the bottom changes. We could click on a few others, and we can see that that updates at the bottom, so we can see exactly what each bot does within the system. I think this one is also a really good example of where the sharing feature could be useful. For example, if someone wanted to recreate a similar GrokBot team, or if I wanted to recreate this GrokBot team on a different account, I could share this page with them as a blueprint. They can explore and see how the setup works and then also instruct their bot in their account to recreate this system by sharing the page with them. So, instead

7:19of just giving someone a document explaining how my bot team works, this can be used essentially as a prompt guide to rebuild this system within a different account. So, there's a look at the four different pages I've built using GrokBot, and I think there's a lot of potential here. For me, the most interesting part isn't just being able to create another document or report, it's that my bot can pull information from the tools it already has access to, analyze it, and turn that into something useful and interactive. The Kit example is really powerful, where I've got all that data now within Grokbot. I don't really ever have to now go into Kit to

7:51do any sort of data analysis. I think that's where pages are a bit different from something like Notion, which I still use to manage all of my projects and information. Pages just give me another way to bring data together and explore it without having to build everything myself, and also without having to leave Grokbot. I'd be interested to hear what your experience is so far with pages. If you've built any pages, let me know in the comments below how you're using it. If you found this useful and you want to see more

8:16Grokbot videos, make sure you subscribe. Thanks for watching, and I'll see you in the next one.