Connect HubSpot, Google Workspace, and Slack with an AI Agent

Connect HubSpot, Google Workspace, and Slack with an AI Agent

Your CRM lives in HubSpot. Your emails, docs, and calendar live in Google Workspace. Your team lives in Slack. Getting these three systems to talk to each other usually means tab-switching, copy-pasting, or building Zaps that break when fields change.

A Slack AI agent connects all three from one place—pulling deal data, drafting follow-ups, updating spreadsheets, and posting results back to Slack without manual handoffs. This guide covers how to set up that connection, what workflows you can automate, and how to avoid the common pitfalls.

The hidden cost of switching between HubSpot, Google Workspace, and Slack

Connecting HubSpot and Google Workspace through Slack AI agents lets you automate workflows where Slack becomes the command center for CRM actions and document management. Rather than bouncing between tabs to check deal status, draft follow-ups, and update pipeline trackers, you query data, update records, and trigger actions using natural language—all without leaving Slack.

The friction adds up quickly. A sales rep checking a deal stage opens HubSpot, then switches to Gmail to send a follow-up, then logs back into HubSpot to update notes, then opens Google Sheets to adjust a forecast. Each switch costs 20-30 seconds and breaks concentration.

Meanwhile, data lives in silos. Notes from a call never make it into the CRM. Follow-up emails sit in drafts. Pipeline reports go stale because updating them takes too long.

What the native HubSpot Slack integration actually does

HubSpot offers a built-in Slack integration you can install from the HubSpot Marketplace. It pushes notifications to Slack channels when forms are submitted, deals change stages, or tasks come due. You can also use /hubspot commands to search for contacts or create basic records.

That said, the native integration has clear boundaries:

• One-way alerts:

  It notifies you about HubSpot activity but doesn't pull data on demand

• No Google Workspace connection:

  Gmail, Calendar, Sheets, and Drive remain separate

• Limited actions:

  You can create records, but complex multi-step workflows aren't supported

For teams that only want HubSpot notifications in Slack, the native integration works fine. For teams that want to act across HubSpot and Google Workspace from Slack, it falls short.

Why Google Workspace belongs in the same Slack workflow

Sales and operations workflows don't end at the CRM. A deal closes in HubSpot, but then someone drafts a contract in Google Docs, schedules an onboarding call in Calendar, sends a welcome email from Gmail, and updates a revenue tracker in Sheets.

Connecting only HubSpot to Slack leaves half the workflow manual. You still tab-switch for every Google Workspace action.

The real efficiency gain comes from treating HubSpot, Gmail, Calendar, Sheets, and Drive as one connected system—accessible from a single Slack message.

Ways to connect HubSpot, Google Workspace, and Slack without code

Several no-code paths exist. Each comes with different tradeoffs for setup time, flexibility, and maintenance.

Native HubSpot Slack integration

The simplest option. Install from the HubSpot Marketplace, authorize your workspace, and start receiving notifications. Good for alerts and basic record creation. No Google Workspace support, no multi-step workflows.

Zapier, Make, and Workato

Automation platforms that let you build multi-step flows connecting HubSpot, Google Workspace, and Slack. You create individual "Zaps" or "Scenarios" for each workflow—like "When a HubSpot deal closes, create a row in Google Sheets and post to Slack."

The tradeoff: you build and maintain each flow separately. When HubSpot fields change or Google Sheets columns shift, flows break and require manual fixes.

Slack Workflow Builder with HubSpot webhooks

A more technical option using Slack's native Workflow Builder plus HubSpot webhook triggers. You configure HubSpot to send JSON payloads to Slack when events occur, then build Slack workflows to process them.

This approach requires comfort with webhooks and JSON. Google Workspace support is limited unless you add additional integrations.

AI agents that live in Slack

An AI agent is an assistant that connects to your tools via API or browser and completes tasks when you ask in natural language. Unlike chatbots that answer questions, agents take action—updating CRM records, drafting emails, creating spreadsheet rows.

You type a request in Slack. The agent identifies the task, shows what it would do, and executes when you confirm. No flow-building required.

How a Slack AI agent unifies HubSpot and Google Workspace

An AI agent reads context from connected tools, understands your request, and executes multi-step workflows across HubSpot and Google Workspace. Then it delivers output in Slack. You stay in one place while the agent handles the tab-switching and data entry.

Here's what that looks like in practice:

• Reads:

  Pulls deal data from HubSpot, emails from Gmail, events from Calendar, files from Drive

• Acts:

  Updates CRM records, drafts emails, creates Sheets rows, schedules meetings

• Delivers:

  Posts summaries, attachments, and confirmations back to Slack

The key difference from automation platforms: you don't pre-build flows. You describe what you want in plain language, and the agent figures out the steps.

How to set up a Slack AI agent for HubSpot and Google Workspace

Setup takes minutes, not days. No IT tickets, no onboarding calls, no implementation timeline.

Step 1. Add the AI agent from the Slack App Directory

Install from Slack's marketplace. Sign in with Slack to claim your agent instance. Each user in your workspace gets their own private agent—conversations and data aren't shared across teammates.

Step 2. Connect HubSpot to your Slack agent

Authorize via OAuth. The agent gains read/write access to contacts, deals, and activities. Credentials are encrypted and stored separately from the AI—the agent can authenticate but never sees raw passwords.

Step 3. Connect Gmail, Calendar, Sheets, and Drive

Same OAuth flow for Google Workspace. Each connection is scoped per user, so your Gmail access doesn't overlap with a teammate's. Connect only the tools you want the agent to access.

Step 4. Assign your first cross-tool task in Slack

Type @Diana Agent pull my open deals from HubSpot and draft follow-up emails in Gmail. The agent shows a preview of what it would do. Hit Enter to run.

You can also ask for simpler tasks: "What's the status of the Acme deal?" or "Schedule a call with the contact from my last closed deal."

Step 5. Schedule recurring workflows

One-off tasks can become scheduled automations. Type @Diana Agent send me a daily HubSpot pipeline summary at 9am. The agent runs the workflow automatically and posts results to Slack on schedule.

Tip: Start with a single recurring workflow—like a daily pipeline summary—to see how the agent handles scheduling before adding more.

Real workflows you can run from one Slack message

Here are actual tasks teams run daily, not hypothetical examples.

Post-call HubSpot updates and Gmail follow-ups

After a sales call, type @Diana Agent log call notes to the Acme deal in HubSpot and draft a follow-up email in Gmail. One message, two tools updated. The agent shows the draft before sending so you can edit.

Daily HubSpot pipeline summary in Slack

Schedule a morning workflow: the agent pulls pipeline data from HubSpot every day at 9am and posts a summary to your sales channel. No manual report-building.

Investor update built from HubSpot and Google Sheets

Type @Diana Agent pull this month's closed revenue from HubSpot, update the investor update template in Sheets, and post the link here. The agent queries HubSpot, populates the spreadsheet, and delivers the link—monthly, on autopilot.

Calendar scheduling triggered by CRM activity

When a deal moves to "Negotiation" in HubSpot, ask the agent to check your Calendar availability and propose meeting times to the contact via Gmail. The agent handles the back-and-forth.

Try Diana free →

Native integrations vs Zapier vs Slack AI agents

Native integrations are limited to single-tool notifications. Automation platforms offer flexibility but require building and maintaining individual flows. AI agents combine breadth with simplicity—you describe what you want, and the agent handles execution.

Permissions, approvals, and audit logs across three tools

Security matters when an agent accesses your CRM, email, and documents. Here's how well-designed agents handle it:

• Credentials:

  Encrypted and stored separately from the AI—the agent can authenticate but never sees raw passwords

• Approvals:

  Sensitive actions like sending emails or updating records prompt confirmation in Slack before execution

• Audit logs:

  Full history of what the agent did, when, and why—exportable for compliance

• Per-user isolation:

  Each employee gets a private agent instance; conversations and data aren't shared across teammates

Diana includes a built-in safety system called The Governor that screens every message before it reaches the AI and blocks suspicious or harmful requests.

Common pitfalls when connecting HubSpot, Google Workspace, and Slack

A few mistakes to avoid:

• Token expiration:

  OAuth tokens expire. Ensure your agent handles re-authentication gracefully without breaking scheduled workflows

• Over-permissioning:

  Only grant the scopes each tool requires. Your agent doesn't require full admin access to HubSpot if it only updates deals

• Notification overload:

  Too many Slack alerts create noise. Use filters to surface only high-priority events

• Ignoring browser-only tools:

  Some tools lack APIs. Look for agents with browser automation that can log in and perform actions on closed systems

• Skipping approval workflows:

  High-stakes actions—like sending emails to customers—benefit from a confirmation step before execution

Run your stack from Slack with Diana

Diana is an AI employee that lives in Slack, connects to HubSpot and Google Workspace via API and browser, and completes tasks—not just answers questions. Add Diana from the Slack App Directory in under 2 minutes. Every employee gets their own isolated agent instance.

Free forever plan. No credit card required. No per-seat charges.

Try Diana free →

Frequently asked questions about connecting HubSpot, Google Workspace, and Slack

Can HubSpot integrate with Slack natively?

Yes. HubSpot offers a native Slack integration for notifications and basic record creation. However, it does not connect Google Workspace tools or execute multi-step workflows across both platforms.

What AI tools integrate with both HubSpot and Google Workspace?

Several AI platforms connect both, including Diana, which works via API and browser automation from inside Slack. The key differentiator is whether the tool answers questions or actually completes tasks.

Does HubSpot have its own AI agent?

HubSpot includes AI features like content assistants and predictive lead scoring. It does not offer a Slack-native agent that also connects Google Workspace for cross-tool workflows.

How do Slack AI agents handle expired OAuth tokens?

Most agents detect token expiration and prompt you to re-authenticate directly in Slack. Well-designed agents handle re-authentication without breaking scheduled workflows—you get a notification, re-authorize, and the workflow resumes.

Can multiple team members use the same Slack AI agent with private data?

Yes. Agents like Diana provision a separate, isolated instance for each user. Your conversations, connected credentials, and data aren't shared with teammates—even though everyone installs from the same Slack app.

What happens if a tool in my workflow does not have an API?

Some AI agents use secure browser automation to log in and perform actions on tools without APIs. Diana, for example, can work with virtually any web-based tool—including legacy or closed systems—by navigating the interface like a human would.