Build a Campus Opportunities Database
Give your existing Grok Bot a public campus events page and have it build a database you can sort and use
Challenge
Build a Campus Opportunities Database
Level: Beginner · No Code · 30 Minutes
Give your existing Grok Bot a public campus events page and have it build a database you can sort and use. The finished table must contain five current events with source links. Grok Bot should enter the records in Notion or Google Sheets, not stop at a chat summary.
What you’ll do and learn:
- Read the source: The Bot uses the browser to open the events page and collect five current listings.
- Fill the database: It creates the table and enters each record in the destination you choose.
- Verify the result: You compare one row with the source and have the Bot fix unsupported values.
Steps:
- Choose a public events calendar from a school, library, city, hackathon community, Luma, or another public source. It must show at least five upcoming events. Copy its URL so you can paste it into the request.
- Choose Notion or Google Sheets as the destination, and note which one you chose. If you do not have either account, use a local file named
campus-opportunities.csvon the Bot’s computer. - Send Grok Bot this request:
> “Using this calendar URL:[PASTE CALENDAR URL], create a table named Campus Opportunities in[NOTION, GOOGLE SHEETS, OR LOCAL CSV]with the next five events. Use the columns Event, Date and time, Location, Audience, Registration URL, Source URL, and Checked at. Checked at means the date and time you verified the event against the source page. Use Unknown when the page does not provide a value. Do not register, contact an organizer, or publish anything.” - If the destination asks you to sign in, open Agent Computer, the Bot’s browser and computer view, and take over for the login or two-factor step. Return control when you are done. Do not put a password or code in chat.
- Open the completed table. Compare one row with the source page, then ask the Bot to correct any missing or unsupported values across all five rows.
- Sort the finished table by date and capture the result.
- If the calendar blocks the Bot, attach a saved PDF or screenshot and repeat the request. The Source URL field should say
Attached copywhen no live URL is available.
You are finished when the destination contains five checked records that can be sorted by date.
What to submit:
- A screenshot of the Grok Bot conversation showing that the database is complete.
- A screenshot of the sorted table with all seven columns and five records visible.
- The calendar URL, or “Attached copy” if you used the fallback, plus one sentence naming the row you checked against it.
Submissions are only open during the event.