Skip to content

Built-in enterprise integrations

Marella connects to the systems your team already uses.

Every integration in this catalogue is built in. Configure the right workspaces, sources and permissions, and Marella can search them.

Built-in catalogue

Choose the systems you want Marella to work with.

Every connection below is already part of Marella. Open one to see what it connects to and what you have to decide when setting it up.

Built in

Amazon S3

Point Marella at approved Amazon S3 buckets and prefixes using least-privilege credentials, and record your region and encryption requirements first.

StorageView connection
Built in

API integration

Marella's built-in API integration moves approved data in and out of the platform, over endpoints, payloads and a service identity that you set.

DeveloperView connection
Built in

Confluence

Sync approved Confluence spaces into Marella, then follow a cited answer back to the page it came from. You choose the content scope during setup.

Knowledge baseView connection
Built in

Email ingestion

Bring approved mailboxes into Marella so messages and their attachments can be searched, with retention and deletion behaviour agreed beforehand.

CommunicationView connection
Built in

Google Drive

Connect approved Google Drive folders and Shared Drives to Marella. Review the OAuth scopes first, then check answers still link to the source file.

Document storeView connection
Built in

Microsoft Teams

Use approved Microsoft Teams channels as a source Marella can read and a place it can answer, once team scope and user identity have been tested.

CommunicationView connection
Built in

Notion

Bring approved Notion pages and databases into Marella, attachments included, with a link back to the original page kept alongside every answer.

Knowledge baseView connection
Built in

OneDrive

Connect approved OneDrive files and folders to Marella, review the Microsoft scopes you are granting, and test what happens when a file is deleted.

Document storeView connection
Built in

SharePoint

Connect approved SharePoint sites and libraries to Marella, and test whether the permissions on those libraries carry across before anyone asks.

Document storeView connection
Built in

Slack

Let Marella read approved Slack channels and answer inside them, with any write action held behind a confirmation step your administrators configure.

CommunicationView connection

Custom integrations

If your team uses it, Marella can connect to it.

If it is not in the list, we can still connect it. We can create a custom integration around its available interface, your security boundary and the job people need to complete.

That includes internal tools, specialist industry software and old systems, not just well-known cloud products.

Plan a custom integration

Custom connection blueprint

Start with the workflow, then choose the route.

Any system
Input
Your system

Cloud, internal, legacy or proprietary

API or webhook01

Connect a supported service interface for data exchange, events or workflow actions.

MCP server02

Expose approved tools to Marella agents with allow, confirm and deny controls.

Database or secure transfer03

Move governed records or files from internal and legacy systems.

Tailored connector04

Build around a proprietary system, unusual data model or specialist workflow.

Output
Marella

Search, answers, agents or workflows

01 · Interface
How the system exposes data or actions
02 · Boundary
What identities, records and operations are allowed
03 · Outcome
What a person or agent needs to accomplish

Connection setup

Every connection still needs configuring.

The connector is ready. The settings still have to match your systems, your content and your people.

  1. 01Identity

    Authenticate the right tenant and map the users, groups or service identities involved.

  2. 02Scope

    Choose the spaces, folders, channels, buckets or records the workflow can reach.

  3. 03Change

    Test edits, moves, new versions, ownership changes and revoked access.

  4. 04Removal

    Confirm deletion and archival behaviour in both the source and Marella.

  5. 05Failure

    Test what happens when a sync fails part way or a file will not read.

  6. 06Evidence

    Check the passages and citations point at the right document and the right version.

Integration FAQ

Integration questions

Which integrations are built into Marella?

Marella includes built-in connections for Amazon S3, API integration, Confluence, Email ingestion, Google Drive, Microsoft Teams, Notion, OneDrive, SharePoint, Slack. Each connection is configured to the approved workspace, content and permission boundary.

Can Marella connect to a system that is not listed?

Yes. Any system your organisation uses can be connected through its API, webhooks, an MCP server, a database or secure file route, or a tailored connector built around the workflow.

What does built in mean?

Built in means the connection capability is part of Marella, rather than a future roadmap item. Setup is still specific to your tenant, authentication, source scope, lifecycle and permission requirements.

How are source permissions handled?

The selected integration is configured around the identities, spaces, folders, channels or records that should be in scope. Permission changes, inaccessible content, updates and removals are tested before wider rollout.

Listed or not, we can connect it.

Tell us what the system is, where data needs to move and what people or agents should be able to do.

Discuss your integration