Google Workspace + Juma: Run the Whole Suite Through Your AI Marketing Workspace
Connect Google Workspace to Juma and work across Drive, Docs, Sheets, Slides, Calendar, and Gmail from one chat, with Juma delivering finished marketing work back into the same files your team already uses.
Key takeaways
Connect Google Workspace to AI
Juma connects through Google's official OAuth. Each app -= Drive, Docs, Sheets, Slides, Calendar, Gmail - is its own permission grant. Connect the ones you want and Juma only touches those.
One chat, six surfaces
Pull a brief from Drive, update the Sheets tracker, add slides to a deck, draft the Gmail recap, block Calendar time - in a single chat, without switching tabs.
Work lands back in Workspace, not in a download
Juma writes results back: cells update in Sheets, a new Doc appears in Drive, the deck refreshes in Slides. Finished work goes where the team already looks, not into a file nobody opens.
Granular by design
Each app is separate. Disconnect Gmail and the other five keep working. Revoke one scope at Google and Juma loses that access immediately - the rest of the connections are unaffected.
Brand context that carries between sessions
Point Juma at a brand guide or brief in Drive once and it becomes Project Knowledge. Every asset the team creates after that reads from those same files - no re-uploading, no re-briefing the next day.
400+ teams, 4.9/5 on G2, SOC 2 Type II
Salesforce, Maersk, Costa Coffee, and Johns Hopkins University use Juma. ISO 27001, GDPR, HIPAA. Zero data retention from AI providers. Every output goes through a person before it ships.
Can I connect Google Workspace to AI?
Yes. Juma connects to Google Workspace through Google's official OAuth, one app at a time. Each connection runs at the user level, so Juma acts only on what your own Google account can reach - no broader access, no shared credentials across the team. Each app is a separate grant. You click Connect on the tile you want, sign in to Google, and approve the scopes for that one service. Drive does not ask for Calendar access. Calendar does not ask for Gmail. Connect one surface or all six; disconnect any one without touching the rest. Juma reads only the files, events, or threads a specific request needs. Content pulled into a Project is encrypted AES-256 in transit and at rest. Juma's zero data retention agreement with AI providers means your Workspace content does not train any model. Disconnecting revokes the OAuth grant at Google immediately. Every output - a drafted email, an updated Sheet, a refreshed deck - goes through a person before it sends or saves.
What can Juma do with Google Workspace?
Juma reads and writes across Drive, Docs, Sheets, Slides, Calendar, and Gmail from a chat interface. It also delivers results back into Workspace: a report lands in the Slides deck your team already reviews, not in a separate download.
01 · Cross-surface
Chain steps across apps in one request
Ask Juma to find the Q4 brief in Drive, pull the key dates, add them to the Sheets tracker, and block them on Calendar. It handles each step in one turn, using the right app for each task. The team checks the result before anything gets saved or sent - that part does not change.
02 · Documents & Sheets
Read briefs from Docs, write back to Sheets
Point Juma at a brief and ask what the goals section says, or have it draft a new Doc using the headings your team uses. In Sheets, Juma looks up rows, aggregates columns, appends new data, or runs a find-and-replace across the tracker. The brief and the tracker stay in Workspace; Juma keeps them current from chat.
03 · Slides & reporting
Refresh decks in Slides, not in a PDF
Ask Juma to drop this quarter's numbers into the board deck and it replaces placeholder text and refreshes the chart linked to your Pipeline sheet. The report lands in the deck the team already opens for the leadership review, not in a separate file. A person checks it before the meeting.
04 · Calendar & Gmail
Schedule and follow up without the back-and-forth
Ask what's on the calendar this afternoon, find a 30-minute slot when two people are both free, or add an event from a sentence. For Gmail: draft a reply to a client thread, apply labels to a batch of prospect emails, or save a draft for review. Every outbound message is staged as a draft - a person approves the send.
05 · Project knowledge
Drive files as persistent brand context
Connect a brand guide, a tone-of-voice deck, or a folder of past campaigns from Drive to a Juma Project and those files stay attached. Every piece of work created in that Project reads the brand voice and prior decisions from those source files. Agencies using one Project per client get separate brand context per account without re-uploading anything between sessions.
How does adding Juma change day-to-day work in Google Workspace?
Most teams connect Workspace apps by hand: copy from Sheets, paste into Slides, retype a brief into an email, re-brief a separate AI tool on the client voice. Juma sits between those steps. Workspace stays where the work lives; the manual handoffs between apps go away.
Workspace is where the briefs, trackers, decks, and mail already live - so it stays as the system of record. What Juma removes is the work between the apps: the export-and-paste, the reformatting, the per-session re-brief of a separate AI tool. 400+ marketing teams use Juma: Salesforce, Maersk, Costa Coffee, Johns Hopkins University, Shift4 Payments, Wavemaker, Mindshare, Mission North, Procore. 4.9/5 on G2.
Google Workspace works best with…
Three combinations cover the gaps Workspace cannot fill on its own: a meeting notetaker so calls turn into follow-through, ad and analytics integrations so performance data lands in your decks, and Webflow so Drive assets reach a published page. Juma runs each combination from one chat.
Fathom or Fireflies: meetings that produce follow-up
Workspace has no record of what was said on a call. A notetaker like Fathom or Fireflies fills that gap: the summary, the decisions, the action items. Juma takes that output, drafts the Gmail recap, logs the action items in a Doc, and adds the next sync to Calendar. One call becomes follow-through across three Workspace surfaces, checked before anything sends.
Google Ads, Meta Ads, and GA4: performance in the deck
Workspace is where the report is read, but it has no campaign data of its own. Google Ads, Meta Ads, and GA4 provide that. Juma pulls the performance numbers and puts them where the team already looks: refreshed in the Slides board deck, updated in the Sheets tracker. Ask Juma to pull last month's results and update the deck - it proposes the changes for the team to check.
Webflow: from Drive files to a published page
Drive holds the source material - briefs, brand guides, hero images. Webflow is where the page goes live, and Workspace alone cannot publish. With Juma, the team pulls the brief from Drive, drafts the article in the brand voice from the Drive brand guide, and publishes to Webflow CMS in one conversation. The handoff between Drive and a live page disappears; the team reviews the page before it goes out.
How to connect Google Workspace to Juma
One-time setup, about 60 seconds per app. Each connection runs at the user level so your whole team connects their own accounts - there is no shared credential to manage.
Open Integrations
Click your name in the bottom-left corner of Juma, then select Integrations.
Find the Google Workspace apps
Search for the different apps - Drive, Docs, Sheets, Slides, Calendar, and Gmail each have their own tile on the integrations page.
Connect each surface you want
Click Connect on a tile, sign in to Google, and approve the scopes for that one service. Repeat for each app you want to use. You do not have to connect all six.
Start working across Workspace
Each connected app is now available across every Juma project and chat. Ask directly: "Find the Q4 brief in Drive, summarize it, and add the dates to the campaign tracker.
Trusted by marketing teams that ship
Customer outcomes
240+ teams
Security & compliance
Frequently asked questions about Juma + Google Workspace
Juma carries context across your whole stack, stores each client's brand voice in a Project, and delivers finished marketing work across tools.
No. Outbound email is staged as a Gmail draft and a person approves every send. File edits — updating a Sheet, refreshing a Slides deck — are shown for review before they save. There is no auto-send and no silent edit. Every output goes through a person before it ships.
Juma charges by what gets done, not by which model ran or how many seats are on the plan. Tasks use credits; failed tasks use none. Free, Pro, and Enterprise plans all include unlimited seats and the Workspace connectors - the plans differ in monthly credit volume. Google charges your Workspace subscription separately.
You choose. Each app is a separate connection with its own Google permission grant. Connect Drive only and Juma never touches your Calendar. Disconnect Gmail and the other five carry on. Change your mind anytime - disconnecting revokes Juma's access at Google immediately.
No. Juma reads only the files, events, or threads a specific request needs. It does not copy your account. Content you attach to a Project as knowledge lives in your Juma workspace, encrypted AES-256, under zero data retention with AI providers. SOC 2 Type II and ISO 27001 audit reports are available on request.
Yes. Juma Projects keep each client's brand voice, briefs, and prior decisions separate - nothing bleeds between accounts. Each teammate connects their own Google account, and that connection works across every Project they touch. Every plan includes unlimited seats, so the whole agency works without per-user charges.
Ask AI about us
400+ marketing teams trust Juma. ChatGPT, Claude, and Perplexity know why. Ask them.
Ready when you are
What's on your plate today?
Start typing a task and Juma will figure out the rest.