How To Use Jasper's Knowledge Base Connectors

If your marketing team relies on a shared drive full of approved messaging docs, product one-pagers, pricing sheets, and brand guidelines, you already know the problem. Those documents change. Positioning gets updated after a launch. Pricing shifts mid-quarter. A compliance team revises approved language. And suddenly, the version sitting in your AI tool is yesterday's truth.

The result: content that references outdated claims, off-message positioning, or retired pricing info from two sprints ago. Someone catches it in review. Or worse, they don't.

When teams produce content manually, one piece at a time, this is manageable. You check the latest doc, copy the right language, move on. But when you deploy agents to generate dozens or hundreds of assets across campaigns, channels, and regions, every piece of content is only as accurate as the knowledge behind it. Agents don't guess; they reference what they've been given. And if what they've been given is stale, the problem scales with your output.

This is one of the core challenges of moving from AI experimentation to system-level execution: agents can move fast, but the intelligence they operate on has to keep up.

That's exactly what Jasper's Knowledge Base Connectors are designed to fix.

This guide walks you through Jasper's Knowledge Base Connectors, what they do, why they matter for teams running AI-powered marketing at scale, and how to set them up so your source documents, your agents, and your finished content stay in sync without the manual upload cycle.

What are Knowledge Base Connectors?

Knowledge Base Connectors let you link folders from Google Drive or Microsoft SharePoint directly to your Jasper Knowledge Base, the foundation of Jasper IQ, the decision intelligence layer that powers every agent workflow. Once connected, Jasper automatically syncs the contents of those folders, including new files, edits, renames, and deletions, so your Knowledge Base always reflects the most current version of your source material.

No manual uploads. No version-checking. No "wait, which doc is the latest?" conversations.

Your shared drive stays your system of record for approved content. Jasper stays continuously aligned with it. And every agent that touches your content operates from the same governed foundation.

Why this matters

In a world where AI systems increasingly shape how brands are discovered and represented—through search summaries, AI-generated answers, and recommendation engines—the accuracy of what you publish isn't just a quality issue. It's an influence issue. Outdated or inconsistent content doesn't just look bad internally. It sends conflicting signals to the AI systems that interpret and surface your brand.

Creating content faster only works if that content is accurate. And accuracy at scale depends on one thing: whether your agents are working from the same source of truth your team already trusts. For most teams, the source of truth isn't one person's drive. It's the shared repository the whole team works from. Connectors now sync directly from there.

Without connectors, keeping Jasper's Knowledge Base current is a manual process. Someone has to remember to re-upload a document every time it changes. Across a team of twenty or fifty marketers, across multiple brands, regions, and product lines, that process breaks down fast. Files get missed. Old versions linger. And the content Jasper produces drifts from what's been approved, which means the signals reaching AI discovery surfaces drift, too.

Knowledge Base Connectors close that gap by turning a manual sync into an automated one. Here's what changes:

Every agent decision starts with current intelligence. Connectors feed directly into Jasper IQ, the layer that embeds brand context, governance rules, and company knowledge into every agent workflow. When your positioning docs are current, every output your agents produce reflects the latest approved narrative. That's how decision intelligence works in practice: not just knowing what to say, but knowing it now.

Teams spend less time correcting and more time shipping. When the source material is current, first drafts come back closer to final. That means fewer review cycles, fewer "this pricing is wrong" flags, and less time spent on cleanup that shouldn't have been necessary.

Knowledge management scales without adding admin overhead. Connector-based syncing removes the need for someone to play librarian, manually uploading, replacing, and organizing files inside Jasper. The folder structure you already maintain in SharePoint or Google Drive does the work.

Jasper Chat finds the right context automatically. With connectors in place, Jasper Chat can proactively search and attach relevant Knowledge Base content when generating responses, so users get grounded outputs without having to hunt for the right reference doc themselves.

Who should use Knowledge Base Connectors?

If your team produces content at volume and relies on shared documentation as the foundation for messaging, positioning, and brand standards, connectors are built for you. A few scenarios where they're especially valuable:

Content and campaign teams generating high volumes of assets across channels that need to reflect the latest product positioning, competitive messaging, or campaign briefs, without manually cross-checking every source doc before every generation.

Brand and compliance teams in regulated industries (financial services, healthcare, pharma, insurance) where approved language changes frequently and off-message content carries real risk. When governance is a requirement, not a nice-to-have, automated knowledge syncing is the difference between scalable compliance and a constant audit loop.

Product marketing teams maintaining positioning documents, battle cards, and launch briefs that feed into content across the organization, and need those updates reflected everywhere, immediately. This is especially critical for teams using Jasper's agents to scale launch execution across regions and segments.

Growth and SEO teams running AI search visibility programs (GEO/AEO) where content needs to be not only optimized for discovery, but grounded in accurate, current product and brand information. When AI systems summarize your content, the claims they surface need to be the ones you've actually approved. Connectors help make sure the Optimization Agent is always working from the right foundation.

If you're already storing your approved marketing documents in Google Drive or SharePoint, connectors let Jasper stay in sync with those documents automatically.

How to set up Knowledge Base Connectors

Setup takes just a few minutes. Once your admin has enabled the integration for your workspace, any user can connect to it. Here's how to get connected.

Step 1: Navigate to your Knowledge Base settings

In Jasper, go to Knowledge Base from the left-hand navigation. This is where all of your workspace's knowledge assets—documents, text entries, URLs, and now connected folders—are managed.

Step 2: Start a new connector

Click Add to Knowledge Base and select the connector option for either Google Drive or Microsoft SharePoint. You'll be prompted to authenticate with your Google or Microsoft account.

Step 3: Authenticate and authorize access

Sign in with the account that has access to the folders you want to sync. Jasper will request read access to the selected folders so it can pull in and monitor your documents. Your files stay in your drive. Jasper reads and indexes them, and it doesn't move or modify them.

Step 4: Select your folders

Choose the specific folders you want to connect. In Google Drive, you can navigate across three tabs: My Drive for your personal folders, Shared with me for folders others have given you access to, and Shared drives for your team's shared repositories. Most teams will want their Shared drives, since that's usually where approved messaging frameworks, product specs, competitive briefs, compliance-approved language, brand voice, and style guide documentation actually live. You can select multiple folders across all three.

Step 5: Confirm and sync

Once your folders are selected, confirm the connection. Jasper will perform an initial sync to pull in the current contents of those folders. From that point forward, any changes you make in the source folder—new files, edits, renames, deletions—automatically flow into your Knowledge Base and into the intelligence layer that powers your agents.

That's it. Your Knowledge Base is now continuously aligned with your shared drive, and every agent workflow built on Jasper IQ benefits immediately.

What the connector looks like in action

Not sure where to begin? Here are three scenarios where connectors save real time and prevent real problems.

1. Product launch messaging that stays current: Your product marketing team maintains a set of launch documents in SharePoint—positioning briefs, feature descriptions, approved claims, competitive differentiators. Connect that folder to Jasper, and every asset your agents generate during the launch pulls from the latest version. When positioning shifts after early customer feedback (and it always does), the updated doc syncs automatically. No one has to remember to re-upload it. And every downstream asset—from the sales one-pager to the paid ad variations built in Jasper Grid—reflects the change.
2. Compliance-approved language in regulated industries: In financial services, pharma, or insurance, approved language isn't optional—it's required. Connect the folder where your compliance or legal team maintains approved messaging, disclaimers, and claim language. When Jasper's agents generate content, they reference the current approved versions. When compliance updates a disclosure, it flows into Jasper without anyone filing a ticket. This is what governed execution looks like at scale: agents operating within guardrails that update themselves.
3. AI search visibility grounded in accurate brand signals: Teams using Jasper's Optimization Agent to improve how their brand shows up in AI-generated search results need content grounded in accurate, current product information and approved messaging. Connect your product documentation and brand guidelines, and the Optimization Agent works from a foundation that's always current. The content it produces both performs well in search and sends consistent, accurate signals to the AI systems that are summarizing and recommending your brand.

Get started

The gap between deploying AI agents and operating them as an intelligent system often comes down to one thing: whether those agents have access to the right knowledge, right now. Jasper's Knowledge Base Connectors solve that by keeping your source of truth and your execution layer in continuous sync so every agent, every workflow, and every piece of content starts from the most current, approved foundation.

If your team stores approved messaging, product information, and brand standards in Google Drive or SharePoint, this is the fastest way to make sure Jasper is always working from the latest version.

Set up your first connector today and see what happens when your intelligence layer and your content engine are always aligned.

Ready to get started? Learn more about connecting your Knowledge Base to Google Drive and SharePoint in the Help Center.