HubSpot SharePoint and OneDrive Integration: The Complete Guide

Your proposals, contracts and project files live in Microsoft 365. Your customer data lives in HubSpot.

And the gap between the two is where documents get lost.

The HubSpot SharePoint and OneDrive integration closes that gap. It's a native HubSpot app that shows Microsoft 365 files directly on contacts, companies, deals and tickets, and lets workflows create folders, upload files and link content automatically.

In this guide you'll learn what the integration does, how to set it up, how to build the workflows that remove the manual filing, and where its current limits are.

What is the HubSpot SharePoint and OneDrive integration?

The HubSpot SharePoint and OneDrive integration is a HubSpot-built app from the HubSpot Marketplace that lets you attach, organise and open Microsoft SharePoint and OneDrive files from CRM records and automate file management with workflows.

Files stay in Microsoft 365. HubSpot stores a link and shows it in context on the record.

That distinction matters. Your SharePoint permissions, version history and retention policies keep working exactly as before. HubSpot simply becomes the place your team finds the right document at the right moment.

Once connected, the integration adds two things to your portal:

1. A SharePoint and OneDrive card in the right sidebar of contacts, companies, deals, tickets and other records.
2. Six workflow actions: create folder, upload file and link item, each available for SharePoint and for OneDrive.

The record card works on every HubSpot plan. The workflow actions need a Professional or Enterprise subscription, because that's where HubSpot workflows live.

Why do documents and CRM records drift apart?

Documents and CRM records drift apart because every stage of a deal produces files, and each team stores them in a slightly different place with no link back to the record.

Here's how it usually plays out.

Sales drafts a proposal in OneDrive. The account owner finalises the contract in a SharePoint library. After close, delivery creates a project folder somewhere else again.

Three months later, a new customer success manager inherits the account and spends an hour hunting for the signed agreement.

Until recently, the fix was middleware such as Make, Zapier or n8n, or a third-party file app from the HubSpot Marketplace. Those still make sense for complex flows.

But for the everyday case ("put this customer's documents where they belong, and show them on the record") HubSpot now handles it natively.

What can you do with the integration?

You can attach Microsoft 365 content to any record manually, and you can automate three things with workflows: creating folders, uploading files and linking existing content.

Let's look at each one.

Attach SharePoint and OneDrive content to any record

From the SharePoint and OneDrive card, you can browse or search Microsoft 365 and link a file or folder to the record in a few clicks.

Once linked, anyone with access can open the file in Microsoft with one click or copy a share link.

Two practical details:

• You can attach up to 20 items per record.
• Folders count as one item, so linking a single well-organised customer folder usually covers everything.

Create folders automatically with workflows

The "Create folder in SharePoint" and "Create folder in OneDrive" actions create a folder the moment a CRM event happens.

Deal created. Stage changed. Company became a customer. Ticket opened. Any workflow trigger works.

You set the folder name with record tokens (for example, associated company name plus deal name) and choose where it lands: the root of a document library or drive, or inside a specific folder.

Because the naming convention lives in the workflow rather than in someone's head, every customer gets the same folder structure.

Upload files automatically with workflows

The "Upload file to SharePoint" and "Upload file to OneDrive" actions take a file stored in a HubSpot file property and send it to a Microsoft 365 folder.

The classic use case is a signed contract. It comes back through e-signature or a form, lands in a file property on the deal, and the workflow drops a copy into the customer's SharePoint folder. Nobody downloads and re-uploads anything.

Link existing content with workflows

The "Link SharePoint item" and "Link OneDrive item" actions attach content that already exists to the record that triggered the workflow.

For OneDrive, that's a file or folder. For SharePoint, you can link a whole site, a document library, or a specific folder or file.

This is the action that handles scale. If you already have a customer site per account, you can attach it to every matching company record in one bulk enrolment instead of clicking through hundreds of records.

Setting up this kind of document automation is what Superwork does for B2B teams every week. Book a HubSpot workflow and integration consultation with Superwork if you'd rather have the folder structure, naming conventions and workflows designed and built for you.

How do you set up the HubSpot SharePoint and OneDrive integration?

Setting up the HubSpot SharePoint and OneDrive integration takes four steps: opt into the beta, install the app from the HubSpot Marketplace, connect your Microsoft 365 account, and add the card to your record layouts.

Here's each step in detail.

Step 1: Opt your account into the beta

A Super Admin needs to enable the Microsoft OneDrive & SharePoint File Integration for HubSpot Records public beta in your HubSpot account's product updates settings.

Until that's done, the app won't behave as described here. We'll update this post when the integration reaches general availability.

Step 2: Install the app from the HubSpot Marketplace

1. Click the Marketplace icon in HubSpot's top navigation.
2. Search for Microsoft SharePoint and OneDrive and open the app page.
3. Click Install.
4. Choose whether to connect SharePoint, OneDrive, or both.
5. Click Connect.

You can start with one and add the other later under Settings → Integrations → Connected Apps → Microsoft SharePoint and OneDrive → Settings → Manage connections.

Step 3: Sign in to Microsoft 365 and authorise HubSpot

Follow the on-screen sign-in to authorise HubSpot against your Microsoft 365 account.

This is where most setup delays happen, so know two things in advance.

It's a user-level app. Each person who wants to use it connects with their own HubSpot login and their own Microsoft 365 account. There's no single admin connection that covers the whole team. Plan a short rollout so every rep and CSM connects on the same day, and check they have the App Marketplace permission (or have requested app access).

Your Microsoft 365 admin may need to grant tenant-wide consent. If your IT team manages app consent tightly (most mid-market and enterprise tenants do), send them the request before the rollout, not after the first person hits a consent error.

Step 4: Add the card to your record layouts

The card doesn't appear on its own.

A Super Admin, or a user with the Customize record page layout permission, needs to add the Microsoft SharePoint and OneDrive card to the right sidebar of each record type you want it on. Deals and companies at minimum; contacts and tickets if service or account management will use it.

Once the card is in place, any connected user can:

1. Open a record and find the Microsoft SharePoint and OneDrive card in the right sidebar.
2. Click + Add.
3. Browse or search for a file or folder.
4. Select it and click Confirm.

The item now appears on the card, ready to open in Microsoft.

How do you automate document filing with HubSpot workflows?

You automate document filing by building three workflows that map to the moments documents matter: create a folder when a deal starts, upload the signed contract when it closes, and link the customer's site when the company becomes a customer.

Here's the pattern we recommend for a typical B2B sales-to-delivery process.

Workflow 1: Create the customer folder when a deal is created

Trigger on deal creation, or on the stage where a proposal is first sent if you'd rather not create folders for every early-stage opportunity.

Add the Create folder in SharePoint action:

1. Choose the Microsoft account.
2. Set the folder name using record tokens, such as associated company name plus deal name.
3. Set the destination to your customers document library root, or a "Clients" folder inside it.

A quick note on naming. Pick a convention that sorts well and that your delivery team will recognise a year from now. Company name first, then deal name or year, works for most teams. Don't put the deal stage in the folder name: stages change and folders don't rename themselves.

Workflow 2: File the signed contract when the deal closes

Trigger on deal stage equals Closed Won.

Add the Upload file to SharePoint action:

1. Set the CRM object to Deal.
2. Pick the file property that holds the signed agreement.
3. Set the destination to the folder created in Workflow 1.

If both actions live in the same workflow, the upload action can use the folder identifier output from the create-folder action. If they're separate workflows, use the folder's sharing URL as the destination.

Workflow 3: Link the customer site to the company record

Trigger on company lifecycle stage equals Customer, or run it once as a bulk enrolment over your existing customer list.

Add the Link SharePoint item action:

1. Set the CRM object to Company.
2. Set the attachment type to Site or Document library.
3. Point it at the customer's site.

Every account manager who opens the company record now sees the delivery team's workspace one click away.

If your process has more moving parts (separate folders per product line, region-specific libraries, a handover from HubSpot to a project tool), talk to Superwork about designing your HubSpot document automation. We map the process first, then build the workflows so they hold up as the team grows.

What are the limits of the integration?

The main limits are that only OneDrive for Business is supported, each user must connect individually, records hold a maximum of 20 linked items, workflow actions require Professional or Enterprise, and the app is still in beta.

When do you still need a third-party tool?

You still need a third-party tool when you want file metadata synced into HubSpot properties, documents generated from templates, a SharePoint folder watched for new files, or two-way sync.

The native integration covers attach, create, upload and link. It doesn't do the rest.

A common setup is to use the native integration for record-level visibility and the standard folder and contract workflows, and add a middleware flow (Make, Zapier, n8n) only for the one or two edge cases that need it.

That keeps the everyday experience inside HubSpot while limiting how much you depend on external tooling.

Frequently asked questions

Does the integration copy files into HubSpot?

No. Files stay in SharePoint or OneDrive, and HubSpot stores a link that appears on the record. Microsoft's permissions and version history continue to apply. The one exception is the upload workflow action, which sends a copy of a HubSpot file to Microsoft 365, not the other way around.

Which HubSpot plans include the SharePoint and OneDrive integration?

The app and the record card are available on all HubSpot products and plans. The workflow actions for creating folders, uploading files and linking items require a Professional or Enterprise subscription.

Can I connect only OneDrive, or only SharePoint?

Yes. During install you choose one or both, and you can add the other later under Settings → Integrations → Connected Apps.

Do all users need to connect their own Microsoft account?

Yes. It's a user-level app, so each HubSpot user signs in to Microsoft 365 themselves. There's no tenant-wide connection made by an admin.

Can workflows create nested folders?

Yes. A create-folder action can target a specific folder as its destination, including a folder created earlier in the same workflow, so you can chain actions to build a customer folder with standard subfolders.

Does it work with personal OneDrive?

No. Only OneDrive for Business accounts inside a Microsoft 365 tenant are supported.

Getting the most out of it

The HubSpot SharePoint and OneDrive integration is only as good as the folder structure and workflow design behind it.

Teams that get value on day one usually did three things first: agreed a naming convention, decided which records get a folder and when, and rolled out the user connection step deliberately rather than hoping people would find the card on their own.

If you want that done properly, book a HubSpot workflow and integration consultation with Superwork. We'll review how your documents move today, design the folder and workflow structure, and build it in your portal so every customer record has its documents exactly where your team expects them.

Source: HubSpot Knowledge Base, Add and use Microsoft SharePoint and OneDrive files in HubSpot.