Gen8

SharePoint integration

Integration · route: configured

The intranet nobody searches, finally searchable

In many organizations SharePoint is where knowledge goes to be forgotten: handbooks, procedures, project files and lists once set up. Gen8 has its own SharePoint integration so a workflow can use that content with document references, within the scope your administrator defines.

Book an introduction
  • Permissions stay in force
  • EU hosting
  • Visible approval

Documents, Knowledge

At a glance

Route: configured
Components: SharePoint (sites, lists, document libraries)

Capabilities

What the integration can do

Sites. Read a designated site's structure: its libraries and lists and their organization.

Lists. Read items — and, if configured, add or update an item. Many SharePoint lists act as small registers for requests, inventory or decisions.

Files. Find and read documents in a designated library and prepare a document in your designated location with its existing metadata.

What does not happen: reorganizing libraries, changing permissions or deleting documents. That is administration, which stays with your administrator.

Inspiration

What you can automate with this

A few examples of work you can hand over through this integration. We work out what fits your organisation together during scoping.

Answer questions from your libraries

A colleague asks a question. The workflow searches the designated document library and answers with a document reference.

Documents in the right place, with the right metadata

A document is prepared in your designated library with its existing metadata. You see the proposal before it is stored.

Maintain a SharePoint list

Many lists are small registers for requests, inventory or decisions. The workflow proposes a new or updated list item.

Does this work look familiar? Or does your process run on another system?

Tell us which work you want to hand over. We help you think through the integration and route, even if your system is not listed here yet.

Book an introduction

Permissions and data

What access is needed

An administrator connects and designates sites, libraries and lists. This especially matters in SharePoint because Microsoft permissions are often broader than necessary, and tenant-wide access is difficult to undo in behavior.

SharePoint permissions should remain authoritative: the integration must not become a way around them. How strictly that works depends on the identity it uses. Verify this during setup rather than assuming it. Gen8 processes in the EU; Microsoft processes content in your tenant.

Control

Where approval is required

Reading as a source needs no approval per question; control lies in selecting sources and who may use the workflow.

Writing — storing a document or creating or updating a list item — follows the usual principle: first a visible proposal, including attached metadata. Metadata is not incidental: a wrong tag in SharePoint makes something unfindable. Every step is logged.

Evidence

What we can demonstrate

SharePoint has its own Gen8 integration with separate tools for sites, lists and files. The route is configured rather than native because it becomes useful only after an administrator designates sites, libraries and lists and checks permissions. Other Microsoft components are covered in Microsoft 365, the Google equivalent in Google Drive, and making content queryable in documents and knowledge. For a system without its own integration: MCP, API and custom development.

gen8 · sharepointdone

Answer a question from the designated library

Plan01Question scoped to included sites and libraries
Action02Site structure read: libraries and lists
Action03Documents searched and read within the questioner's permissions
Action04Answer drafted with document and location reference
Reflect05Recording in a list affects metadata: proposal submitted
Answer with source · the list item awaits approval

Frequently asked questions

Does the workflow access the entire tenant?

We aim to avoid that. We configure designated sites, libraries and lists, and your administrator should choose deliberately.

Will everyone see everything?

That must never be the result. SharePoint permissions should remain authoritative; verify this during setup rather than assuming it.

Can the workflow clean up documents?

No. Deleting and reorganizing are administrative actions we do not configure.

Does this work with OneDrive or Google Drive too?

Both have their own integration with the same structure. See Microsoft 365 and the Google Drive integration.

Which systems do you use?

Tell us which process you want to connect. We explain which route fits, which permissions are needed and where people keep making decisions.

Book an introduction
  • Reply within one business day
  • No obligation