Amazon S3
Point Marella at approved Amazon S3 buckets and prefixes using least-privilege credentials, and record your region and encryption requirements first.
Built-in enterprise integrations
Every integration in this catalogue is built in. Configure the right workspaces, sources and permissions, and Marella can search them.
Built-in catalogue
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.
Point Marella at approved Amazon S3 buckets and prefixes using least-privilege credentials, and record your region and encryption requirements first.
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.
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.
Bring approved mailboxes into Marella so messages and their attachments can be searched, with retention and deletion behaviour agreed beforehand.
Connect approved Google Drive folders and Shared Drives to Marella. Review the OAuth scopes first, then check answers still link to the source file.
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.
Bring approved Notion pages and databases into Marella, attachments included, with a link back to the original page kept alongside every answer.
Connect approved OneDrive files and folders to Marella, review the Microsoft scopes you are granting, and test what happens when a file is deleted.
Connect approved SharePoint sites and libraries to Marella, and test whether the permissions on those libraries carry across before anyone asks.
Let Marella read approved Slack channels and answer inside them, with any write action held behind a confirmation step your administrators configure.
Custom integrations
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 integrationCustom connection blueprint
Cloud, internal, legacy or proprietary
Connect a supported service interface for data exchange, events or workflow actions.
Expose approved tools to Marella agents with allow, confirm and deny controls.
Move governed records or files from internal and legacy systems.
Build around a proprietary system, unusual data model or specialist workflow.
Search, answers, agents or workflows
Connection setup
The connector is ready. The settings still have to match your systems, your content and your people.
Authenticate the right tenant and map the users, groups or service identities involved.
Choose the spaces, folders, channels, buckets or records the workflow can reach.
Test edits, moves, new versions, ownership changes and revoked access.
Confirm deletion and archival behaviour in both the source and Marella.
Test what happens when a sync fails part way or a file will not read.
Check the passages and citations point at the right document and the right version.
Integration FAQ
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.
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.
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.
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.
Tell us what the system is, where data needs to move and what people or agents should be able to do.
Discuss your integration