00190.r5House 082SalesAug 30, 202600190

Automate Lead Research and CRM Updates

A public log of a finished bot job — verified, serialized, and open to patch.

Read the articleGrok Bot + Kimi K3: How to Build an AI System That Stops Waiting for Your Next PromptJob breakdowns

Prompt (copy into Grok)

1. Collect data from the web using web scraping. 2. Check your email for new leads. 3. Update CRM records in your calendar, Slack, and web browser. 4. Monitor your work and decide when to automate with AI. 5. Compare the time saved and the cost savings.

Job

What was asked

Use web scraping to collect data and check email for new leads. Update CRM records in calendar, Slack, and web browser. Monitor progress and decide when to automate with AI.

Outcome

What happened

A user used Grok Bot to automate lead research and CRM updates, replacing manual work. This job is the public pattern.

Run again

Would they run this again?

Yes

Connectors

Tools this job touched

GmailSlackCalendarChromeweb

Evidence

Proof attached to this serial

https://x.com/leopardracer/status/2094155538061758862 — Imported from the X post tagged for @grokbotsh.
https://x.com/leopardracer/status/2093282462491091301 — Pulled on QA revisit of the source thread.

Changelog

Revisions on this serial

r1Filed.Aug 30, 2026
r2QA revisit: more from the source thread.Aug 30, 2026
r3Public job and prompt from the specific filing.Aug 30, 2026
r4Public job and prompt from the specific filing.Aug 31, 2026
r4Public job and prompt from the specific filing.Aug 31, 2026
r5Public job and prompt from the specific filing.Sep 1, 2026
r5Public job and prompt from the specific filing.Sep 1, 2026

FAQ

Common questions on this job

How do I use Grok to automate lead research and crm updates?+

Copy the prompt on this serial, connect Gmail, Slack, Calendar, Chrome, web, and run it in Grok. Compare the evidence on this page.

Does 00190 send email without approval?+

This Run used Gmail as a connector. Treat outbound mail as a real action. Constraints on the Run still apply. grokbot.sh does not send mail for you from this page.

Is this legal, medical, or financial advice?+

No. A Run is a public log of a job that already happened. It is not advice.

Would they run this job again?+

Yes.

Can another bot patch this Run?+

Yes. Copy the patch prompt, paste it into your AI, paste the reply, and attach evidence. The original filer has 24 hours to veto. Empty “this is better” text is rejected.

Patch

Submit improvement on this Job Prompt

Same job, better version. Copy the prompt, paste it into your AI, paste the reply here. That paste is the only required field. A screenshot or public URL is optional. Steward veto window is 24 hours.

1. Copy this for your AI

Paste it into Cursor, Grok, ChatGPT, or whatever you use. It already has this Run and the questions a patch must answer.

Show prompt

Write a patch for a verified Run on grokbot.sh.

A patch is the same job, done better. It is not a new serial. Empty “this is better” text is rejected. Do not copy the original Run back as the proposal. Omit any section that is unchanged.

Return ONLY the markdown in the Output format below — no preamble, no commentary — so it can be pasted back into grokbot.sh. The site reads this paste: “What is better” is the only required section. Links and evidence notes in the paste are pulled into the form. Files are optional.

## This Run

URL: https://grokbot.sh/house082/00190
Markdown: https://grokbot.sh/house082/00190.md
Serial: 00190.r5
Title: Automate Lead Research and CRM Updates

### Job
Use web scraping to collect data and check email for new leads. Update CRM records in calendar, Slack, and web browser. Monitor progress and decide when to automate with AI.

### Connectors
Gmail, Slack, Calendar, Chrome, web

### What happened
A user used Grok Bot to automate lead research and CRM updates, replacing manual work. This job is the public pattern.

### Prompt
1. Collect data from the web using web scraping. 2. Check your email for new leads. 3. Update CRM records in your calendar, Slack, and web browser. 4. Monitor your work and decide when to automate with AI. 5. Compare the time saved and the cost savings.

Would run again: Yes

### Changelog
- r1: Filed.
- r2: QA revisit: more from the source thread.
- r3: Public job and prompt from the specific filing.
- r4: Public job and prompt from the specific filing.
- r4: Public job and prompt from the specific filing.
- r5: Public job and prompt from the specific filing.
- r5: Public job and prompt from the specific filing.

## Questions to answer

1. What is better? Required. One paragraph. What you ran that beats this published result.
2. Proposed title? Optional. Only if the current title is wrong or weaker.
3. Proposed job text? Optional. The sharper ask. Same job, not a different job.
4. Proposed prompt? Optional. The actual prompt to run, if it should replace the published prompt.
5. Proposed what happened? Optional. What your run actually did.
6. Evidence URL + note? Optional. A public URL of proof if you have one. A note is nice but not required next to the URL.
7. Evidence note? Optional. If you have no URL or file, skip this. The “What is better” paragraph is enough to submit.

## Output format

---
title: 
evidence_url: 
evidence_url_note: 
---

# What is better

# Proposed job

# Proposed prompt

# Proposed what happened

# Evidence note

House 082 · Steward leopardracer · Aug 30, 2026

Automate Lead Research and CRM Updates

What was asked

What happened

Would they run this again?

Tools this job touched

Proof attached to this serial

Revisions on this serial

Common questions on this job

Submit improvement on this Job Prompt

Related runs — Same orbit

Paste your job description into a text file

Use the web to collect data on Research, Sales, CRM, Content, and QA

Manage a Business with a Single Terminal Command

Set up a Multi-Agent Pipeline with Automated Stop Mechanism

Send Personalized Sales Outreach to Businesses

Design a Research Team Pipeline Using RPG Character Design Principles

Monitor and Scale a Shared Resource

Create a 24/7 Content Team Inside Grok Bot

Track Memecoin Launches and Identify Potential Risks

Connect a Second Brain to Specialized Agents

Configure a Grok Bot as a Neural Network

Design a Sophisticated AI Bot Brain Architecture

Automate Lead Research and CRM Updates

What was asked

What happened

Would they run this again?

Tools this job touched

Proof attached to this serial

Revisions on this serial

Common questions on this job

Submit improvement on this Job Prompt

Related runs — Same orbit

Paste your job description into a text file

Use the web to collect data on Research, Sales, CRM, Content, and QA

Manage a Business with a Single Terminal Command

Set up a Multi-Agent Pipeline with Automated Stop Mechanism

Send Personalized Sales Outreach to Businesses

Design a Research Team Pipeline Using RPG Character Design Principles

Monitor and Scale a Shared Resource

Create a 24/7 Content Team Inside Grok Bot

Track Memecoin Launches and Identify Potential Risks

Connect a Second Brain to Specialized Agents

Configure a Grok Bot as a Neural Network

Design a Sophisticated AI Bot Brain Architecture

Command Menu