Create Customized Grok Bot Employees for Organization and Automation

JSON· Markdown· House 038 · Steward Voxyz_ai · Voxyz founder the AI-native future · QA Enriched

Job

Create customized employees using Grok Bot to automate tasks such as refund tracking, digital cleanup, and meeting assistance. Use existing email and Google Drive audit prompts and customize them to meet specific requirements. Implement rules for user approval and notification preferences.

Connectors

Gmail

What happened

A user created customized Grok Bot employees for refund tracking, digital cleanup, and meeting assistance. The user set up each employee to perform specific tasks, such as scanning order and refund emails, auditing email and Google Drive, and sitting in on meetings. The user implemented rules for user approval and notification preferences, including requiring approval before deleting, unsubscribing, or sending emails, and sending notifications for tasks that require user action.

Constraints

only 3 notification types, no pinging user except for stuck tasks

Would run again

Yes

Evidence

https://x.com/Voxyz_ai/status/2090423614684160305 — Imported from the X thread tagged for @tryreallybot.

Changelog

r1: Filed. (Aug 20, 2026)
r2: QA revisit: more from the source thread. (Aug 20, 2026)
r2: Public job and prompt from the specific filing. (Aug 20, 2026)
r3: Public job and prompt from the specific filing. (Aug 20, 2026)

FAQ

How do I use Grok to create customized grok bot employees for organization and automation?

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

Does 00210 send email without approval?

This Run used Gmail as a connector. Treat outbound mail as a real action. Constraints on the Run still apply. really.bot 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.

What constraints were on this job?

only 3 notification types, no pinging user except for stuck tasks

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 this Run

Same job, better version. Copy the prompt, paste it into your AI, paste the reply, attach evidence. 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 really.bot.

A patch is the same job, done better, with evidence. 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 really.bot.

## This Run

URL: https://really.bot/house038/00210
Markdown: https://really.bot/house038/00210.md
Serial: 00210.r3
Title: Create Customized Grok Bot Employees for Organization and Automation

### Job
Create customized employees using Grok Bot to automate tasks such as refund tracking, digital cleanup, and meeting assistance. Use existing email and Google Drive audit prompts and customize them to meet specific requirements. Implement rules for user approval and notification preferences.

### Connectors
Gmail

### What happened
A user created customized Grok Bot employees for refund tracking, digital cleanup, and meeting assistance. The user set up each employee to perform specific tasks, such as scanning order and refund emails, auditing email and Google Drive, and sitting in on meetings. The user implemented rules for user approval and notification preferences, including requiring approval before deleting, unsubscribing, or sending emails, and sending notifications for tasks that require user action.

### Prompt
Create customized employees using Grok Bot to automate tasks such as refund tracking, digital cleanup, and meeting assistance. Set up each employee to perform the following tasks: scan order and refund emails, audit email and Google Drive, and sit in on meetings. Implement the following rules for all employees: ask for approval before deleting, unsubscribing, or sending emails; provide users with three types of notifications: chase this money? delete these files? need your answer here?

### Constraints
only 3 notification types, no pinging user except for stuck tasks

Would run again: Yes

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

## Questions to answer

1. What is better? Required. One paragraph, tied to the evidence. 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 here. A public URL of proof, plus one sentence on what it proves. You can also attach files on the site.
7. Evidence note? Optional. If the screenshot stays private, describe what it showed. Redact PII.

## Output format

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

# What is better

# Proposed job

# Proposed prompt

# Proposed what happened

# Evidence note