Skip to content
NagentNagent
Log inSign upHire your AI Growth Team
NagentNagent
Log inSign up

AI marketing agents that work with HubSpot, Slack, and Google Workspace

8 Minutes read
Published:
HubSpot's own agents fit teams whose records live in HubSpot. Lindy fits agents that live in Slack and Gmail. Relevance AI fits teams that build their own. Google's agents fit Docs and Gmail work. Here is what each connects to, the permissions to grant, and what to test.
PB
Pratap BeheraNov 15, 2026·8 min read
AI marketing agents that work with HubSpot, Slack, and Google Workspace

If HubSpot is your system of record, its own agents need the least setup and draw on connected Slack and Google Workspace information. For agents that live in Slack and act in Gmail and HubSpot, choose Lindy. To build your own across thousands of apps, choose Relevance AI. For work centred on Docs and Gmail, use Google's Workspace agents. For a coordinated marketing team with approvals in Slack, a team platform such as Nagent fits.

"Works with" means different things on different vendor pages: reading data, taking actions, living inside the chat tool, or sending approvals there. This guide separates those, compares the options tool by tool, and lists the permissions a marketing agent should get. Every vendor fact was read on the vendor's own site on 24 October 2026. We make Nagent and cover it in its own section; the MIRA page shows how its Marketing team uses connected tools.

What does "works with HubSpot, Slack and Google Workspace" actually mean?

Check which of these five levels a vendor means:

  1. Reads data. Pulls contacts, lists, deals, messages or documents as context.

  2. Takes actions. Creates a contact, drafts an email, posts a message, writes to a sheet.

  3. Lives in the chat tool. People ask the agent in Slack and it answers there.

  4. Approvals in the chat tool. The agent's held work can be approved or declined in Slack.

  5. Learns from the tool. Slack channels or Drive folders become part of the agent's knowledge.

Most vendors do the first two. Fewer do all five, and fewer still let you limit each action to specific agents.

How do the main options compare?

All facts and prices checked 24 October 2026.

HubSpot Agent Hub (Breeze)

  • What it is: HubSpot's home for its agents, including Content, Campaign, Nurture, Prospecting, Customer and Data agents, plus Agent Builder (HubSpot AI).

  • HubSpot: native; agents work on HubSpot CRM, content and email data.

  • Slack and Google Workspace: HubSpot says its AI uses integrated workspace information such as Google Workspace, Microsoft 365 and Slack. Breeze Assistant itself runs inside HubSpot and its mobile app (Breeze Assistant).

  • Best for: teams whose contacts, email and landing pages live in HubSpot.

  • Pricing: Agent Hub is included in Starter, Professional and Enterprise; Marketing Hub Professional lists $800 and $890 a month with 3 core seats and a required $3,000 onboarding fee (HubSpot pricing).

  • Limitation: Slack and Google data serve as context; HubSpot's pages do not describe its agents working inside Slack.

Lindy

  • What it is: AI agents across inbox, Slack and meetings.

  • HubSpot: 39 actions, such as creating and updating contacts, companies, deals and tickets (Lindy HubSpot).

  • Slack: 35 actions, including an approval request with buttons sent to a channel; you mention Lindy in a channel to start it (Lindy Slack).

  • Google Workspace: 23 Gmail actions, with drafting and sending as separate actions (Lindy Gmail); the pricing page claims 1,500+ integrations.

  • Best for: teams that want agents for inbox, follow-up and Slack-based requests.

  • Pricing: Team from $29.99 a month per active user for 3,000 credits each, credits pooled (Lindy pricing).

  • Limitation: you design each agent's job; marketing planning is not packaged.

Relevance AI

  • What it is: a platform for building an AI workforce of agents.

  • HubSpot, Slack and Google: its integrations page claims 2,000+ integrations, naming Slack and Salesforce, and shows HubSpot, Gmail and Google Calendar logos (Relevance AI integrations).

  • Best for: teams with time to build and maintain agents.

  • Pricing: one Enterprise plan through sales (Relevance AI pricing).

  • Limitation: we could not confirm individual HubSpot or Slack action lists on its integrations page.

Google Workspace agents

  • What it is: custom agents used across Docs, Gmail and more, and Studio for building flows across Workspace apps (Google Workspace AI).

  • HubSpot and Slack: not named on that page; it names Microsoft 365, Salesforce, SAP and Jira as business apps agents can connect to.

  • Best for: teams whose work lives in Docs, Sheets, Drive and Gmail.

  • Pricing: listed per user per Workspace plan; Enterprise through sales.

  • Limitation: not a marketing system; CRM and ad work sit elsewhere.

Salesforce Agentforce

  • What it is: agents on the Salesforce platform. Salesforce owns Slack.

  • Slack: Slack's own AI agents page says Agentforce in Slack "will be available soon" and to talk to sales; third-party agents are available from the Slack Marketplace (Slack).

  • HubSpot and Google: not a fit if HubSpot is your CRM.

  • Pricing: Foundations $0; Flex Credits $500 per 100,000; per-user add-ons from $125 a month (Agentforce pricing).

  • Limitation: built for Salesforce customers.

Sierra builds customer-facing conversational agents for service and revenue (Sierra). It is not a marketing agent for internal HubSpot, Slack and Workspace work.

Which permissions should a marketing agent get in each tool?

Grant the narrowest set that does the job:

HubSpot

  • Read contacts, lists, companies and deals.

  • Create and update contacts and notes.

  • Create email drafts, not sends, at first.

  • No delete, no list purges, no workflow edits.

Slack

  • Read only the public channels you choose; never all channels by default.

  • Post in named channels and in reply threads.

  • Approvals as buttons, so typing "ok" in a thread does not approve anything.

Gmail

  • Read and draft. Sending only after a record of clean drafts.

  • No delete or trash.

Google Drive, Docs and Sheets

  • Read a named folder of brand and product documents.

  • Write to one named reporting sheet.

Write down who owns each connection. If it was authorised with a person's own account and they leave, it breaks.

What should you test in a two-week trial?

  1. Connect HubSpot, Slack and Google with the permissions above.

  2. Ask the agent in Slack for a weekly campaign report from HubSpot and a Google Sheet. Check every number against the source.

  3. Ask it to draft a nurture email for one HubSpot list. Check that the draft uses your facts and voice and does not send.

  4. Ask it to read your brand folder in Drive and summarise your positioning. Check it against what you know.

  5. Approve one action from Slack. Confirm the record shows who approved it and when.

  6. Revoke one permission. Confirm the agent says it cannot do the job instead of failing silently.

  7. Count the minutes you spent briefing, fixing and approving.

What goes wrong with these integrations?

  • Duplicate sends. HubSpot sequences and an agent sending from Gmail reach the same contact in the same week. Fix: one system owns sending.

  • Channel oversharing. An agent reading every Slack channel pulls in conversations that should not become agent knowledge. Fix: choose channels explicitly and leave private channels out.

  • Permissions too wide. A connection granted "all actions" lets any agent delete. Fix: tick only needed actions and limit each to the agents that need it.

  • Expired connections. OAuth tokens expire or are revoked, and the agent quietly stops. Fix: a visible status per connection and an alert when it fails.

  • Numbers without sources. A report quoting HubSpot figures nobody can trace. Fix: every figure cites its source record.

For a broader comparison of suite agents and dedicated platforms, read what an AI agent platform is compared with AI tools.

Where does Nagent fit?

Nagent is multiplayer AI for growth: people and AI agents in one shared context, delivering the number. It covers all five integration levels above for these three tools, with approvals that follow each agent's level.

  • Connect through Composio. Gmail, Slack, HubSpot, Google Sheets and Drive are among hundreds of tools via Composio, plus your own API. You tick each action agents may call and narrow each one to named agents.

  • Nagent for Slack (Beta). People ask agents in Slack; a message naming no agent reaches the Whole team room. Held replies wait in Slack for someone allowed to approve. The app reads only the public channels an admin chooses into the Knowledge Hub; private channels are not read.

  • HubSpot stays your CRM. SERA reads Nagent's own lead records; HubSpot connects as a tool, and CRM data import is not built.

  • A marketing team, not one agent. MIRA, the AI Marketing Chief of Staff, routes work to DRIS, NIA, HOOK (Beta) and Echo (Beta), and writing to CREA's Content team. Agents start at L2 Assist, and a person approves every customer-facing step below L5 Lead.

What it does not do: it does not replace HubSpot as your CRM or email engine, and it does not post to social media (MOXA is coming soon). Cost is in credits; see pricing and integrations.

Frequently Asked Questions

Do HubSpot Breeze agents work inside Slack?

HubSpot's pages describe its AI using Slack and Google Workspace information as context, and Breeze Assistant running in HubSpot and its mobile app. They do not describe the agents working inside Slack.

Can I approve AI agent work from Slack?

Several tools support it. Lindy offers an approval request with buttons in a channel, and Nagent for Slack (Beta) holds agent replies in Slack until someone allowed to approve does so.

Can AI marketing agents read private Slack channels?

Choose tools that read only the channels you pick. Nagent for Slack does not read private channels; inviting it to one lets it answer there and nothing more.

Which AI agents work with HubSpot and Gmail without hurting domain reputation?

Any that let one system own sending, start with drafts, and send from a verified domain. Avoid two systems emailing the same contact.

See MIRA's team work from your HubSpot, Slack and Google setup: book a demo.

Continue learning

Related agents

Agents that match this read.

Browse all 200+ agents
Select Category
Marketing

Nagent With Slack: Ask AI Agents Where Your Team Talks

Keep Slack and add an agent team inside it. Mention Nagent in a channel, name an agent, and approve its reply in the thread. Beta, with plain limits.

Content

Can AI content agents post to LinkedIn and HubSpot with an approval step?

Yes, but the approval has to sit in the right place. LinkedIn's API publishes on creation, so approval must happen before the call. HubSpot drafts by default, and its formal approvals need an Enterprise edition.

Marketing

Nagent With Google Search Console: What DRIS Reads

Keep Google Search Console and add an agent team on top. DRIS reads your clicks and queries daily, ranks the fixes, and a person approves each one.

Marketing AI

AI Agents vs. Marketing Automation: What's the Real Difference?

Marketing automation platforms execute what you have already decided. AI agents for marketing do the work around the decision, then bring it to a person to approve. Here is where each layer sits, and why one lonely agent is not enough.

AI Strategy

Best AI platforms where a small marketing team and AI agents work together in one workspace

Six platforms where a small marketing team and AI agents can share one workspace, compared on shared context, approvals, coverage and pricing: Nagent, HubSpot Agent Hub, Jasper, Lindy, Relevance AI and Salesforce Agentforce.

Sales

Nagent With HubSpot: AI Agents That Work With HubSpot

How Nagent's AI agents work with HubSpot: two ways to connect, what agents can read and change, what waits for approval, and what Nagent does not do.