Agents In Use
What’s new todayLast update
82 use cases added today

Grok Bot turns ten years of calendar history into a Notion CRM

Gaurav Munjal asked Grok Bot to turn ten years of calendar meetings into a tagged Notion contact database. He reported about 1,000 entries from the first three years after 2.5 hours.

Source published x.comAgent: Grok Bot
OUR ADAPTATION

Suggested prompt

Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.

Review my calendar history in batches and build a Notion contact database from people I have met. Include the meeting context, LinkedIn profile, current role, and useful tags. Track progress and mark uncertain identity matches for my review.

Evidence at a glance

Sourced account
Source poster / publisher
Gaurav Munjal (@gauravmunjal)
Original account
Read the source ↗
Published
Source link checked
Reported result
Munjal reported that after 2.5 hours Grok Bot had processed the first three of ten calendar years and added about 1,000 Notion entries.
Human involvement
The post does not describe a review or approval step for the calendar access, identity matches, profile details, or resulting database.

A linked account supports attribution. It does not mean we independently reproduced its result.

Report an issue with this caseOpen correction email

Opens your email app with the case link included. Nothing is sent automatically.

How the agent did it

  1. Ask Grok Bot to work through each meeting in ten years of calendar history.
  2. Add each person met to a Notion database with their LinkedIn profile, current activity, and tags.
  3. After 2.5 hours, Munjal reported about 1,000 entries from the first three years.

Gaurav Munjal described asking Grok Bot to rebuild a contact archive from a decade of calendar meetings. He wanted each person he had met added to a Notion database, with their LinkedIn profile, what they were doing currently, and tags.

After two and a half hours, Munjal reported that the bot had worked through the first three years and added about 1,000 entries. That is a substantial partial result, not a completed pass over the full decade. The post does not say how many distinct people remained, how duplicates were handled, or whether profile matches and current-role descriptions were checked.

The useful idea is turning years of meeting history into structured relationship records without manually opening every event. For a similar job, use a read-only calendar connection or an export, save progress in batches, and check names and profile matches before relying on the database. Those are cautious adaptations, not steps Munjal reports taking. His post supports the volume and time he observed; it does not establish the archive's completeness or accuracy.

Prompt
Suggested prompt (written by Agents In Use, not the author's)

Source: X · Gaurav Munjal (@gauravmunjal)

Frequently asked questions

How many calendar years did the bot finish?

Munjal said it had processed the first three years of his ten-year calendar history after two and a half hours.

What did the Notion records include?

He asked for each person he had met, their LinkedIn profile, what they were doing currently, and tags.

Were the contact details independently checked?

The post does not describe a review of profile matches, current roles, duplicate contacts, or the finished database.

More details

About this account

Grok Bot read calendar meetings and created Notion contact entries with profile information and tags, according to Munjal's post.

GrokBot.dev reproduces and attributes Munjal's first-hand X post, including its result and publication date. The original X URL returned 403 to automated access. This is a suggested prompt by Agents In Use, not the author's prompt.

Credit: Gaurav Munjal (@gauravmunjal) on X

Source published

Added to Agents In Use

Source checked

Tools and topics

Grok Bot · Calendar · Notion

Calendar history · Contact database · Relationship management

Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.