Connect merlon to the tools you already run.
Governed document processes shouldn't force you to abandon your stack. merlon connects to your identity provider, storage, ERP, e-signature, and messaging tools — so files stay in one controlled workspace while the systems around them keep working. Browse the catalog, filter by category, or search for a specific tool.
Connected, not copied
An integration should reduce the number of places your sensitive documents live — not add another. merlon connects to your systems over authenticated, least-privilege links so a document stays governed in one place while identity, context, and events flow between tools.
Identity flows in
Your IdP is the source of truth for who exists and what they can do. SCIM keeps membership in sync and deprovisioning automatic.
Documents stay put
Storage connectors reference and govern files in place rather than sprawling extra copies across drives and inboxes.
Events flow out
Webhooks and automation tools react to state changes — a signature completed, an approval granted — in the systems you already watch.
Find an integration
Search by name or filter by category. Status badges show what's generally available today, in beta, or on the roadmap.
Okta
SAML SSO and SCIM provisioning for centralized identity and automatic deprovisioning.
Microsoft Entra ID
Azure AD SSO with group-based access mapping and SCIM user lifecycle sync.
Google Workspace
SSO via SAML/OIDC and directory sync for teams on Google Workspace.
SharePoint
Govern documents from SharePoint libraries in place, with mapped permissions.
Google Drive
Reference and route Drive files through governed workflows without duplication.
Dropbox
Import from and sync approved documents back to Dropbox folders.
Box
Connect Box as a governed source for enterprise content workflows.
Slack
Approval requests, reminders, and status notifications delivered in channel.
Microsoft Teams
Native cards for approvals and sign-off nudges inside Teams.
Outlook
Send documents into governed workflows straight from an email.
SAP
Keep approvals and vendor records consistent with your SAP ledger.
Abacus
Swiss ERP connector for finance approvals and document exchange.
Bexio
Sync SME accounting records with document approval workflows.
NetSuite
Reconcile vendor agreements and authorizations with NetSuite.
DocuSign
Route documents to DocuSign and capture the signed original with its trail.
Adobe Acrobat Sign
Send for signature via Adobe and return the executed document to merlon.
Skribble
Swiss/EU qualified electronic signatures (QES) for regulated agreements.
Zapier
Trigger and react to merlon events across 6,000+ apps, no code required.
Make
Build multi-step scenarios that respond to signatures and approvals.
Webhooks & API
Subscribe to events and drive merlon directly from your own systems.
Availability and status are indicative and may vary by plan and region.
From connect to live in three steps
Authorize the connection
An admin authorizes merlon against your tool using SAML, OAuth 2.0, or an API key — always with the minimum scopes needed.
Map access & events
Map identity groups to merlon roles, choose which documents flow, and select the events you want to emit or receive.
Go live & monitor
Turn the connection on. Every action it performs is written to the audit trail, so you can see exactly what moved and when.
Your identity provider stays the source of truth
Rather than managing a second set of users, merlon federates with your IdP. Members sign in with SSO, their group memberships map to least-privilege roles, and SCIM provisioning creates and — crucially — deactivates accounts automatically. When someone leaves in your directory, their merlon access is gone in the same beat.
SAML 2.0 & OIDC
Enterprise SSO with your existing login and MFA policy.
SCIM provisioning
Automatic account create, update, and deactivate.
Group mapping
IdP groups translate into scoped merlon roles.
Enforced MFA
Inherit your IdP's multi-factor requirements everywhere.
Don't see your tool? Build the connection.
Every integration is built on the same public API and webhook system you can use directly. Subscribe to events, react in real time, and drive merlon from your own services. Here's a webhook payload you'd receive when a document is signed.
- Base URL
https://api.merlon.ch/v1— regional:api.us.merlon.ch,api.eu.merlon.ch- Auth
- API keys and OAuth 2.0 client credentials, scoped per vault.
- Events
document.created,document.signed,workflow.approved,access.revokedand more.- Delivery
- Signed webhook payloads with retries and replay protection.
// Delivered to your endpoint on signature { "event": "document.signed", "id": "evt_9b0271e4", "created": "2026-07-27T14:22:10Z", "data": { "document_id": "doc_4f21a8", "vault": "vlt_ch_8f21a4", "version": 4, "signers": ["gc@acme.com"], "audit_hash": "e410…aa" } }
The auth methods integrations use
Every connection uses an authenticated, least-privilege method appropriate to the tool it links.
- SAML 2.0
- Enterprise SSO for identity providers such as Okta, Microsoft Entra ID, and Google Workspace, including signed assertions and enforced MFA.
- OpenID Connect (OIDC)
- Modern OAuth-based single sign-on for providers and applications that prefer OIDC over SAML.
- SCIM 2.0
- Automated user and group provisioning and deprovisioning so directory changes propagate without manual work.
- OAuth 2.0
- Delegated, scoped access for storage, productivity, and API integrations using the client-credentials and authorization-code flows.
- API keys
- Per-environment keys, scoped per vault, for server-to-server automation and custom builds.
- Signed webhooks
- Outbound event delivery with payload signatures, delivery retries, and replay protection.