SharePoint Site connector

Use your SharePoint Site data for reporting, automation and AI.

Data Panda brings the lists, libraries, pages and permissions of a single SharePoint site together with the data from the rest of your business. From one place, we turn site-level content into dashboards, automations, AI workflows and small apps your operations, compliance and project teams use every day.

About SharePoint Site

The Microsoft 365 site that also acts as a small database.

A SharePoint site is the unit Microsoft 365 hands a team when it needs a place to work: documents, pages, news, and the lists that sit underneath them. The Microsoft Graph SharePoint surface treats each site as an addressable resource at /sites/{site-id}, with /lists, /lists/{list-id}/items, /drives, /pages and /permissions hanging off it. Anyone who has ever opened a SharePoint site has seen the document library on the left rail; what often goes unnoticed is the dozen lists on the same site that the compliance team, the IT team and the HR team treat as a real database.

That is where SharePoint sites get interesting to report on. The vendor register that procurement maintains for the supplier-onboarding queue is a list. The asset inventory IT touches when a laptop changes hands is a list. The HR joiner-and-leaver intake the people-team built in an afternoon is a list. So is the project tracker the PMO refreshes on Friday and the contract-renewal log finance keeps next to the signed PDFs. Each one is structured data with columns, content types and an audit trail, sitting in a site nobody outside the team ever opens. Pulling a site's list items into a warehouse joins those records to deals, employees, suppliers and assets in the rest of the stack, so the queue lives in one place and the cross-system reporting works without copy-pasting from a list view into Excel.

What your SharePoint Site data is for

What you get once SharePoint Site is connected.

List and library reporting

Lists, list items, document libraries and permissions of a site joined to the records they describe.

Vendor register from the procurement site joined to invoices in the ERP and contracts in the document library
Asset list from the IT site joined to the user the device is currently assigned to in Entra ID
Library content age and sharing footprint per folder, with the largest items called out

Intake and queue automation

Let SharePoint list items trigger the work they were always meant to drive, without one person watching a list view.

New row in a vendor-onboarding list opens a record in finance and a security review in the right queue
Status change on the project-intake list pushes the next stage to the team site that owns the work
Closed-won deal in the CRM appends a row in the customer-onboarding list with the agreed scope and owner

AI workflows

Put a site's real lists and documents behind AI that respects the permission model, instead of a generic assistant.

Q&A on the policy library and the related list items, scoped to what the user is allowed to see on the site
Auto-fill of new list rows from the document or email a colleague forwarded into the queue
Summary of a long contract or report into the matching list row, with the source link kept on the field

Custom apps on your data

Small internal tools on a site's lists and libraries for people who do not want to live in the SharePoint UI.

Vendor-onboarding queue app on top of the procurement list, with sign-off and document-attachment tracking
Asset-handover app on the IT list that walks the new owner through the device, accessories and software entitlements
Project-intake app that turns a SharePoint list into a transparent queue with SLA and owner assignment

Use cases

Use cases we deliver with SharePoint Site data.

A list of concrete reports, automations and AI features we have built on SharePoint Site data. Pick the one that matches your situation.

Vendor registerProcurement's supplier list joined to invoices in the ERP, contracts in the library and the buyer that owns the relationship.

Asset inventoryThe IT-team's device list joined to Entra ID for the current owner, with last-seen date and warranty status.

HR joiner intakeThe people-team's onboarding list joined to the HRIS record, with the open onboarding tasks and accountable manager.

Project intake queueThe PMO's intake list joined to deal or customer record, with stage, sponsor and SLA per request.

Contract-renewal logFinance's renewal list joined to the signed contract in the library and the supplier or customer record.

Document library healthLibrary size, item count, growth and stale folders per site, with the biggest documents called out.

External-share inventoryExternal sharing links on the site's libraries, ranked by recipient domain, link type and last-access age.

List-permission mapLists with broken permission inheritance and the members granted access outside the site default.

Page and news activityModern pages and news posts on the site, with view counts, last-edit author and the audience targeting that applies.

List-to-flow inventoryLists wired to a Power Automate flow, with the trigger, run frequency, owner and last-failure date.

Real business questions

Answers you will finally get.

What's in the SharePoint Lists on this site?

The site's lists with their definitions, columns, content types and item counts, plus the rows themselves. Procurement, IT, HR and the PMO see their vendor register, asset inventory, joiner intake and project queue as proper rows in the warehouse, not as a list view nobody outside the team ever opens. The columns the team built up over time (status, owner, due date, supplier ID) become joinable fields against the rest of the stack.

How do the documents on this site relate to the records around them?

Each library is a Graph drive with items, versions and permissions, addressable next to the lists on the same site. The contract in the library joins the renewal row in the list and the supplier in the ERP. Compliance and finance stop guessing whether the canonical PDF lives on the site, in someone's OneDrive or in an email.

Who can see what on this site, and which rights are inherited?

Permissions per site, library, list and item, with the inheritance state and the link type for external shares. The records-management lead sees which lists were broken out of the site default and given to a smaller group, and which libraries still have an external link from a supplier review three projects ago.

Value for everyone in the organisation

Where each function gets value.

For finance leaders

Contract libraries, signed quotes and the renewal log on a finance site reportable next to the supplier or customer record. Finance sees which contracts on the site miss the signed PDF or the renewal addendum, and which list rows are open beyond the agreed lead time.

For sales leaders

Account or deal sites with the proposal in the library and the onboarding tasks in the list joined to the CRM record. Sales sees which prospects opened the proposal stored on the site, and which onboarding rows are still open after the deal closed.

For operations

The vendor register, the asset list, the joiner intake and the project queue from the team's SharePoint site, joined to the ERP, the HRIS, the directory and the CRM. Ops runs cross-system reporting on the lists that already drive the work, instead of asking each team to export a list view.

Ideas

What you can automate with SharePoint Site.

Pair with Exact Online

Match the SharePoint vendor register to Exact Online suppliers

The procurement site's vendor list is joined to the supplier master in Exact Online on supplier name and VAT number. Finance sees which list rows have no Exact record yet (a vendor onboarded on the site but never set up for invoicing) and which Exact suppliers exist without a row on the site (a supplier paid for years that never went through the official intake), so the next supplier-master cleanup starts with a list rather than a meeting.

Pair with HiBob

Wire the SharePoint joiner-intake list to HiBob onboarding

The HR site's joiner-intake list is joined to the HiBob employee record on email and start date. People-ops sees which intake rows have no HiBob record yet (a joiner submitted on the site but not set up in payroll) and which HiBob employees joined without an intake row (a hire that skipped the official onboarding queue). The IT, facilities and access-card tasks attached to the row land in the right queue on day one instead of waiting for a manager to chase them.

Pair with HubSpot

Push closed-won HubSpot deals into the SharePoint customer-onboarding list

A closed-won HubSpot deal appends a row to the customer-onboarding list on the right SharePoint site, with the deal owner, agreed scope and start date copied across, and the SharePoint item id written back on the deal. Customer success sees the new account on the queue the day the deal closes, and the proposal already lives in the document library next to the list, so onboarding starts on the canonical site instead of in someone's mailbox.

Pair with Salesforce

Mirror Salesforce account changes onto the SharePoint customer site

Owner changes, renewal dates and account-tier shifts on a Salesforce account are mirrored onto the matching SharePoint customer site: the responsible AM is updated on the contract-renewal list, the renewal-date column moves with the deal, and the tier change shows on the account page header. The next person who opens the site sees the same picture as the one Salesforce shows, instead of a snapshot from the day the site was created.

Pair with monday.com

Sync a SharePoint project-intake list with monday.com boards

Rows added to the PMO's project-intake list on SharePoint create an item on the matching monday.com board, with status, owner and due date kept in sync both ways. The intake stays where the requesters file it (a familiar SharePoint list view) while delivery teams keep planning on the monday board they already use, instead of one team copying rows by hand into the other tool every Monday morning.

Pair with Slack

Post SharePoint list activity to the right Slack channel

New rows, status changes and overdue items on flagged SharePoint lists post a compact update in the Slack channel that owns the topic, with a deep link back to the row on the site. The procurement, IT or HR team stops relying on someone watching the list view, and the conversation about the item happens next to the row that triggered it.

Data model

Tables we make available.

These are the 2 tables we currently pull from SharePoint Site into your warehouse. Query them directly in SQL, join them to the rest of your stack, or build reports on top.

Lists
Sites

Missing a table you need? We can extend the sync. Tell us what is missing and we will build it for you.

Your existing tools

Your data lands in a warehouse. Your BI tools read from it.

You keep the reporting tool you already have. We connect it to the warehouse where your SharePoint Site data lives.

Power BI Microsoft

Fabric Microsoft

Snowflake Data warehouse

BigQuery Google

Tableau Visualisation

Excel Sheets & pivots

Three steps

From SharePoint Site to answers in three steps.

Connect securely

OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.

Land in your warehouse

Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.

Reporting, automation, AI

We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.

Two ways to work with us

Pick the track that fits how you work.

Track 01

Self-serve

We set up the foundation. Your team builds on top.

SharePoint Site connector configured and running
Warehouse set up in your cloud account
Clean access for your Power BI, Fabric or Tableau team
Documentation on what's in the data model
Sync monitoring so you're warned before reports break

Best fit Teams that already have a BI analyst or data engineer and want to own the build.

Track 02

Done for you

We build the whole thing, end to end.

Everything in Self-serve
Dashboards built to the questions your team actually asks
Automations between your systems
AI workflows scoped to real tasks your team runs
Custom apps where a dashboard does not cut it
Ongoing delivery at a pace that fits your team

Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.

Before you book

Frequently asked questions.

Who owns the data?

You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.

How fresh is the data?

Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.

Do I need a warehouse already?

No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.

How is this connector different from the tenant-wide Microsoft SharePoint one?

The Microsoft SharePoint connector reports across the whole tenant: site sprawl, Teams-spawned sites, external-share inventory and Power Automate flow audits. This connector is scoped to a single SharePoint site and goes deep into its lists, list items, libraries, pages and permissions, which is what you want when a specific procurement, HR, IT or PMO site is the operational source of truth for a process you want in the warehouse.

Do custom list columns and content types come through?

Yes. The Graph site/{id}/lists endpoint exposes columns, content types and lookup relations, and listItem responses include the field values under the fields facet. The custom columns a team built up over time (status, supplier ID, due date, owner) land as proper warehouse columns rather than as opaque JSON, so the joins to the ERP, the CRM and the HRIS work without remapping every row.

Are permissions and external-share links part of the sync, or only the data?

Permissions are first-class on the Graph SharePoint surface: each site, library, list and item carries its grantees, link types and inheritance state. The connector lands those alongside the rows, which is how the list-permission map and the external-share inventory work. The records-management lead sees which lists broke out of the site default and which libraries still hold an external link from a supplier review three projects ago.

GDPR-compliant

Data stays in the EU

You own the warehouse

A first deliverable live in four to six weeks.

We review your SharePoint Site setup and the systems around it. Together we pick the first thing worth building.

Book a call See our other connectors