Four Bots at a conference. Chases notes, sends nothing.
Conference desk team
Handles a conference presence: sessions tracked, meetings booked, and every conversation written down before it is forgotten.
Conference desk team
Handles a conference presence: sessions tracked, meetings booked, and every conversation written down before it is forgotten.
Bots
- Schedule Grok Bot
- Meetings Grok Bot
- Notes Grok Bot
- Follow Grok Bot
Conference room group chat
- Schedule Grok Bot
- Meetings Grok Bot
- Notes Grok Bot
- Follow Grok Bot
Google Calendar
HubSpot
Notion
Gmail
Job
Schedule Grok BotGrok Bot
Holds the team schedule and flags clashes and unstaffed slots.
Google Calendar
Meetings Grok BotGrok Bot
Tracks requested meetings and which are unconfirmed.
HubSpot
Notes Grok BotGrok Bot
Chases the note for every meeting held and names what is missing.
Notion
Follow Grok BotGrok Bot
Drafts a specific follow-up per conversation, never a template. Never sends.
Gmail
Routines2
Clash check
Flag schedule clashes and unstaffed slots for the event week.
Note chase
List meetings held today with no note filed, and who owns each.
Skills2
find-skills by vercel-labs… · Fetch at run · View on Skillselion
handoff by mattpocock… · Fetch at run · View on Skillselion
Notes
Sidebar section
Events
Prompt Installer for Grok Bot
Paste the prompt into Grok Bot. This is not one-click OAuth and nothing is installed on this site.
# Grok Bot Teams installer
Set up a team for me called Conference desk team. Create the named Bots, then the group chat, then save the routines.
Ask me only for things you cannot see. Do not start OAuth. If a connector is missing, tell me to connect it in Settings, then Plugins.
From https://botteams.ai (events-conference). Source: https://github.com/ellelion/botteams.
## 1. Create these Bots
Create each Bot below. Use the names exactly, including any prefix. After create, set Name, Title, and Description on the profile, then tell me to set the avatar.
A Bot is a single persistent, named agent. Conversation is the task; Title is the one-line job; Description holds durable rules and approvals.
### Conference desk · Schedule Grok Bot
(Named "Conf · Schedule" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Calendar
Job:
Holds the team schedule and flags clashes and unstaffed slots.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Conference desk · Schedule Grok Bot
- Title: Holds the team schedule and flags clashes and unstaffed slots.
- Description: Holds the team schedule and flags clashes and unstaffed slots. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
Then tell me to open Edit Profile and set the avatar. You cannot stamp a custom image yourself unless I attach one.
If you create this Bot from an existing Bot, ask the new Bot to set those profile fields after create.
### Conference desk · Meetings Grok Bot
(Named "Conf · Meetings" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): HubSpot
Job:
Tracks requested meetings and which are unconfirmed.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Conference desk · Meetings Grok Bot
- Title: Tracks requested meetings and which are unconfirmed.
- Description: Tracks requested meetings and which are unconfirmed. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
Then tell me to open Edit Profile and set the avatar. You cannot stamp a custom image yourself unless I attach one.
If you create this Bot from an existing Bot, ask the new Bot to set those profile fields after create.
### Conference desk · Notes Grok Bot
(Named "Conf · Notes" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Notion
Job:
Chases the note for every meeting held and names what is missing.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Conference desk · Notes Grok Bot
- Title: Chases the note for every meeting held and names what is missing.
- Description: Chases the note for every meeting held and names what is missing. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
Then tell me to open Edit Profile and set the avatar. You cannot stamp a custom image yourself unless I attach one.
If you create this Bot from an existing Bot, ask the new Bot to set those profile fields after create.
### Conference desk · Follow Grok Bot
(Named "Conf · Follow" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Gmail
Job:
Drafts a specific follow-up per conversation, never a template. Never sends.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Conference desk · Follow Grok Bot
- Title: Drafts a specific follow-up per conversation, never a template.
- Description: Drafts a specific follow-up per conversation, never a template. Never sends. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
Then tell me to open Edit Profile and set the avatar. You cannot stamp a custom image yourself unless I attach one.
If you create this Bot from an existing Bot, ask the new Bot to set those profile fields after create.
## 2. Create this group chat
Open a group chat with two to six of the Bots above. Do not add more than six.
### Conference room group chat
Members (4, two to six Bots): Conference desk · Schedule Grok Bot, Conference desk · Meetings Grok Bot, Conference desk · Notes Grok Bot, Conference desk · Follow Grok Bot
## 3. Sidebar section
You cannot create sidebar sections. When the Bots and group chat exist, tell me to Move to, then New section.
I will name that section exactly: Events.
Ask me to move the group chat and Bots into it.
## 4. Routines (confirm card required)
Ping each owner Bot with the routine they own so they can save it.
A routine is owned by one Bot, and one Bot can own up to 50 of them. A confirm card will appear. I will confirm each one.
Do not assume a routine is saved until I confirm.
### Clash check
Owner Bot: Conference desk · Schedule Grok Bot
Schedule: Every weekday at 08:00
Prompt to save (I will confirm the card):
Flag schedule clashes and unstaffed slots for the event week.
### Note chase
Owner Bot: Conference desk · Notes Grok Bot
Schedule: Every day at 19:00
Prompt to save (I will confirm the card):
List meetings held today with no note filed, and who owns each.
## 5. Connectors and how far they go
Connectors are account-wide. They must already be connected.
If any are missing, tell me to connect them in Settings, then Plugins, first.
Do not walk an OAuth flow from this prompt.
Every Bot on this account can reach every connected tool. The lists above are which Bot is expected to use which, not a second OAuth and not a boundary.
- Calendar: Draft. Use Calendar for drafts only. Leave every draft unsent and every change unsaved so a human can review it.
- HubSpot: Ask before send. Use HubSpot only after a human says yes in the chat. State exactly what you are about to do, wait for the reply, then act.
- Notion: Draft. Use Notion for drafts only. Leave every draft unsent and every change unsaved so a human can review it.
- Gmail: Draft. Use Gmail for drafts only. Leave every draft unsent and every change unsaved so a human can review it.
Human: the lines above are instructions, not permissions. In Grok Bot open Settings, then Plugins, and disable the write tools for Calendar, Notion, Gmail. That switch is account-wide and it is the only one that actually stops a write.
## 6. Skills
Skills live under Settings → Plugins → Yours, and they are per Bot. Enable the ones listed here for the named Bots. Reference a skill with /.
You cannot flip the human Notifications toggle. Tell me to leave Settings → “Get notified when this Bot finishes or needs input” on.
Do not pin or hide a Bot unless I say so. Hide does not pause routines.
Sidebar sections are human-only: tell me to Move to → New section. A group chat holds two to six Bots. An account holds 50 Bots and group chats combined. One Bot can own 50 routines. Confirm cards stay on me.
If a workflow should be demonstrated later, mention Teach a task after the first success (browser workflows).
Connect the Skillselion connector first if any skill below is Fetch at run (Settings → Plugins). Do not start OAuth from this prompt.
### find-skills
https://skillselion.com/skills/vercel-labs/skills/find-skills
Creator: vercel-labs
Scope: every Bot on this team (team scope).
Do not install. When this job comes up, use the Skillselion connector to search/load `skill:vercel-labs/skills#find-skills`. Connect Skillselion in Settings → Plugins first.
### handoff
https://skillselion.com/skills/mattpocock/skills/handoff
Creator: mattpocock
Scope: every Bot on this team (team scope).
Do not install. When this job comes up, use the Skillselion connector to search/load `skill:mattpocock/skills#handoff`. Connect Skillselion in Settings → Plugins first.
## 7. Also
Standing instructions for every Bot on this team:
- Never email attendees without a human yes.
- Never change a booking or a contract.
## Done when
- Named Bots exist
- Named group chat exists ("Conference room group chat", two to six Bots)
- I have created section "Events"
- Each routine has a confirmed save (or I declined)
- Connectors listed above are already connected
Uninstall: delete the Bots and group chats in the Grok Bot sidebar.
There is no remote uninstall from this catalog.Teams that share these connectors
- Field events
Runs small in-person events where the budget and the guest list are the two things that quietly go wrong.
LumaGoogle Calendar
RampGmail
- Event sponsorship
Tracks what was bought at an event and whether any of it was delivered.
HubSpot
RampNotion
Gmail
- Webinar desk
Runs a webinar end to end: registrations watched, reminders drafted, and the follow-up ready before the call ends.
LumaZoom
Gmail
Google Calendar



