AI Agents and Assistants
What is an AI agent? A plain-English guide for business owners
What an AI agent is, how it works, where it helps a small business, the risks, and a 7-point check to see if you are ready for one.
AI Features & Bots
AI Slack Bot for Google Workspace
Ask in Slack to find a Drive file, answer from a Doc or check a calendar, within scopes your admin approves.
Hunting for the right Drive file or checking someone's calendar should not mean leaving the conversation. This bot answers in Slack from approved Drive files and Docs, finds files and checks Calendar, all within the OAuth scopes your Google Workspace admin approves. It never reaches beyond those scopes. The code is delivered to your repository, so you own it.
- Find Drive files and answers from Docs without leaving Slack
- Check Google Calendar from a Slack thread
- Works only within scopes your Google Workspace admin approves
$3,250
20–30 working days
Optional maintenance $249/mo
What it is
AI Slack Bot for Google Workspace answers your team's questions in Slack from approved Drive files and Docs, and runs simple actions on Google Workspace data, such as finding a file or checking Calendar, within the OAuth scopes an admin approves. It never reaches beyond the scopes your admin approves.
Why businesses buy it
Teams on Google Workspace and Slack lose time switching between them, and files get duplicated because nobody can find the original. Answers buried in Docs are asked about again and again. A bot that searches and answers from Drive inside Slack saves that time and keeps people working from the right version. The written scope fixes the folders, scopes, actions and testing before you order, so your admin approves exactly what the bot can reach.
Problems this solves
Staff hunt through Drive folders for the latest version of a file
The bot finds files and answers questions from approved Drive files and Docs, inside Slack. People ask in a channel or direct message instead of clicking through folders.
Checking calendars means jumping between Slack and Google
Simple actions, such as checking Calendar, run from Slack within the OAuth scopes an admin approves. Your team gets what it needs without switching tabs.
Admins hesitate to grant a bot broad access to Google data
The bot never reaches beyond the scopes your admin approves. Field mapping is documented, access uses keys you control, and testing runs on sandbox or test records.
A good fit if
Your team works in Slack but keeps documents in Google Drive, and finding the latest version of a file is a daily question.
You want a few simple Google Workspace actions available from Slack, chosen by you.
A Google Workspace admin can approve OAuth consent for only the scopes you agree.
A technical contact on your side can review the build and receive the code.
Not the right fit if
You need cited answers over up to 2,000 Drive documents with permission groups. See AI Knowledge Agent for Google Workspace.
You want meeting notes and action items captured and routed to owners. See AI Meeting Agent for Google Workspace.
You want new hires guided through onboarding. See AI Employee Onboarding for Google Workspace.
Your answers live in Notion rather than Drive. See AI Slack Bot for Notion.
How it works
- A Google Workspace admin grants OAuth consent for the agreed scopes on a 30-minute call. Drive, Docs, Gmail and Calendar data outside those scopes stay unread.
- Approved Drive files and Docs, up to 100 documents or 200 web pages, become the bot's answer source.
- Up to five intents are built from your use cases, for example finding the latest pricing deck in Drive or checking when the next planning meeting is.
- People mention or message the bot in Slack, and replies arrive in the thread with a link to the file where relevant.
- Requests outside its intents are handed to the person or channel you name.
- 40 documented test questions run before launch, and the code is delivered to your repository.
What you provide within 72 hours
Your portal lists these the moment you order. Delivery starts the working day after everything is in and your access is checked.
- Google Workspace OAuth consent from an admin for the agreed scopes.
- A Google Workspace admin for a 30-minute setup call.
- Slack admin access to install the bot.
- The Drive folders and Docs to answer from, and whether Gmail or Calendar data is needed.
- Target users, use cases and your top 20 questions with approved answers.
- A technical contact for review, a handoff destination and one decision-maker.
- An API key for your own AI model account (for example OpenAI or Google Gemini), created for this build with a spending limit.
The 72-hour rule. Send everything on your checklist, including access, within 72 hours of ordering so your build starts on time.
Timeline
Start
Intake verified; scopes, folders and intents agreed.
Weeks 1–2
Answers from Drive and Docs built; intents coded.
Week 3
Bot installed in Slack; Google Workspace actions tested.
Weeks 3–4
40 test questions, pass or fail results shared.
Week 4
Technical review and two rounds of changes.
Go-live
Live in Slack, code in your repository, recorded handoff.
| Option | Delivery time | Price |
|---|---|---|
| Standard | 20–30 working days | $3,250 |
| Express | 15–25 working days | $3,800 |
| Rush | 10–20 working days | $4,400 |
What you receive at handover
- The AI Slack bot for Google Workspace, live in your Slack workspace
- A two-way Google Workspace connection with documented field mapping, plus up to one more system
- Access granted through admin-approved OAuth scopes and keys you control
- A test report on sandbox or test records, with forty pass/fail test questions
- An admin guide and the recorded 60-minute handoff session
- 30 days of post-launch support
Expected benefits and how to measure them
- Can save time spent searching Drive for files
- Helps admins keep Google access tightly scoped
- Lets people check schedules and documents without leaving Slack
- File-finding requests
- Count 'where is the file' messages in team channels for two weeks before and after launch.
- Bot actions per week
- Take weekly counts of searches and Calendar checks from the bot's logs.
- Answers handed to a person
- Compare handoffs with total questions each week to see where approved files fall short.
Before you start: Count file-finding questions in Slack over two weeks. List the Drive folders and Docs you plan to approve.
These are things to track, not promised results. Outcomes depend on your data, your team and your market.
Running costs
The build is $3,250, paid once. Running costs are roughly $30 to $150 a month in your own accounts for AI model usage and hosting, depending on use.
Google Workspace and Slack plans are unchanged. AI usage during build and testing is billed to your accounts.
Ask about running costsCustom requirements
More than five intents, extra scopes or custom Google Workspace objects outside the mapping, or a second chat channel need a written Change Quote, sent of a note at checkout. Larger or bespoke projects go through the Custom AI request form instead.
Request a custom versionKeep it running
Monthly maintenance covers monitoring, fixes and change hours for a new Drive folder, an extra intent or a scope change your admin approves. The change hours scale with the build. It starts after the included support period and can be cancelled any month.
$249/mo (the minimum fee, includes 2 change hours)
Optional. Starts after the post-launch support period. Cancel any month.
How maintenance worksHow this compares
| Do it yourself with a SaaS tool | Hire a custom agency | Upmark Labs | |
|---|---|---|---|
| Price | A Slack app for Google files bills per user | A contractor builds a bot by the hour | Ours is one fixed price, shown before you buy |
| Scopes | Whatever the app requests | Set by the developer | Ours uses only the scopes your admin approves |
| Actions | Fixed by the vendor | Built to the brief | Ours runs the five intents you choose |
| Code | Rented by the month | Depends on the contract | Ours delivers the code to your repository |
Questions about this product
Can the Slack bot find files in our Google Drive?
Yes, within the folders and scopes agreed at intake. Finding a file can be one of the five intents: someone asks in Slack, and the bot replies in the thread with the matching Drive file and a link. Files outside the approved folders are never returned.
Does the Google Workspace Slack bot read email?
Only if Gmail is within the scopes your admin approves, which is optional. The build works without it. If you include Gmail, its use is written into the agreed mapping and limited to the intents you chose, so the bot cannot wander through mailboxes outside that purpose.
Can the bot check Google Calendar from Slack?
Yes, if Calendar is within the approved scopes and you choose it as an intent, for example asking when the next planning meeting is. The bot reads only the calendars in the agreed mapping and replies in the Slack thread. Any change to events is limited to what that mapping allows.
What does our Google Workspace admin need to approve?
OAuth consent for the specific scopes agreed at intake, such as access to certain Drive folders and Calendar. The admin grants it on a 30-minute setup call, and can review or revoke it from the Google admin console whenever they choose.
What does the Google Workspace Slack bot cost to run?
Roughly $30 to $150 a month in your own accounts for AI model usage and hosting, depending on how much your team uses it. Google Workspace and Slack subscriptions are unchanged, and we take no per-user fee after the one-time build.
How soon can the Google Workspace Slack bot launch?
The standard, Express and Rush delivery times are shown in the price panel before you order, and the clock starts after a verified intake. Approving the OAuth scopes and naming the Drive folders during intake lets the build begin on time, because the bot's answers are built from those folders.
Who owns the Google Workspace bot's code?
You do. The code is delivered to your repository at launch, with an admin guide and the documented scope mapping, and your technical contact reviews it before handover. It remains yours even if you never take maintenance, so your developers can extend it later.
Guides on this topic
All guides Find the file without leaving Slack.
Order AI Slack Bot for Google Workspace and your team gets Drive, Docs and Calendar answers in Slack, always inside the scopes your admin approves.
Works well with
AI Features & Bots
AI Custom Team Assistant
Creates a low-cost private assistant for your team, loaded with your instructions and knowledge.
Employee Lifecycle
AI Employee Onboarding
Runs new-hire onboarding checklists, documents and first-week guidance.