Does Lexnus work in Slack?

Yes. An Admin connects your Slack workspace once. People then get notifications as direct messages, approve or reject requests with buttons, and can ask Lex questions in a direct message.

Which AI assistants can connect to Lexnus?

Any client that speaks the Model Context Protocol, including Claude, ChatGPT, Cursor and VS Code. See the MCP reference for setup.

How do I know a webhook came from Lexnus?

Every delivery carries an HMAC-SHA256 signature over its timestamp and body, made with a secret shown to you once when you create the webhook. Your endpoint checks the signature before trusting the request.

Does Lexnus support SAML?

Single sign-on uses OIDC, which Microsoft Entra ID, Okta and Google Workspace all support. SAML is not available.

Can we use our own AI provider?

Yes. An Admin can switch from the default, Mistral hosted by Lexnus in the EU, to Claude, OpenAI or Azure OpenAI with your own key. Whichever provider you use, it extracts facts. Rules decide compliance.

Is there a Word add-in?

Not yet. A Word add-in and an Outlook add-in are on the roadmap. Today, contracts are drafted and exported as Word documents, and reviewed in Lexnus, in Slack or in an AI assistant.

Integrations | Lexnus

Where your team works

1

Slack

An Admin connects your Slack workspace once, for the whole account. People are matched to their Slack accounts by email. Each person then chooses which notifications reach them as direct messages.

Approval requests arrive with Approve and Reject buttons, so a contract can be unblocked without leaving Slack. Signed-contract notices can go to a channel. And Lex, the Lexnus assistant, answers in a direct message: ask about a contract, or share a file to add it to Lexnus. Lex acts as you, with your role, and asks you to confirm before anything is sent for signature.

2

AI assistants over MCP

Claude, ChatGPT, Cursor, VS Code and other MCP clients connect to Lexnus and use your playbooks directly: analyse a document, draft from a playbook, file a contract, send it for signature. Every call runs as an identified person and is recorded. Setup, tools and limits are in the MCP reference.

3

E-signature through Scrive

Send contracts for signature from Lexnus, with BankID, MitID and qualified electronic signatures among the options. Your team uses the Lexnus Scrive account by default, or an Admin connects your own. See Signing and Obligations.

For your own systems

1

Webhooks

An Admin points Lexnus at an HTTPS endpoint and chooses the events to send. A new webhook receives nothing until it is verified with a signed test request. Every delivery is signed with HMAC-SHA256 so your endpoint can check it came from Lexnus.

Failed deliveries are retried for about an hour and a quarter. After ten failures in a row, the webhook is switched off and its owner is told. The delivery log shows each attempt and the response it got.

2

REST API

The API is the one the Lexnus application uses. Authenticate with a developer token from Account settings → Developers, or with an OAuth token. A call can do what the person behind the token can do, and no more. Requests are rate-limited per account. A refused request says when to try again.

For IT

1

Single sign-on

Sign in through Microsoft Entra ID, Okta, Google Workspace or any OIDC provider. An Admin can require single sign-on for your email domains, which turns off password sign-in for them.

2

Directory sync

Connect Okta, Microsoft Entra or any SCIM 2.0 provider and users and groups are provisioned automatically. An Admin sends IT a setup link that works for 24 hours, without IT needing a Lexnus account.

3

Your choice of AI provider

By default, Lexnus uses Mistral, hosted by Lexnus with EU data residency. An Admin can switch the account to Claude by Anthropic, OpenAI, or OpenAI on Azure with your own key. The provider extracts facts from contracts. It never decides whether they comply — the rules do.

Webhook events

Approval requestedA rule needs sign-off on a contract version.

Approval decidedAn approver approved or rejected.

Contract createdA new contract exists in Lexnus.

New version publishedA contract has a new version.

Contract signedEvery party has signed.

Contract finalisedA contract was marked executed.

Renewal dueA renewal reminder date has arrived.

Contract expiredA contract reached its end date without renewing.

On the roadmap

These are planned, not available today.

Microsoft WordRoadmapCheck a draft against your playbook without leaving Word.

Microsoft OutlookRoadmapCheck a contract that arrives by email.

Microsoft TeamsRoadmapNotifications and approvals in Teams.

DocuSign and Adobe SignRoadmapMore e-signature providers alongside Scrive.

Salesforce and HubSpotRoadmapStart a contract from the deal it belongs to.

Google Drive, SharePoint and ZapierRoadmapConnections to where your documents and workflows already live.

Need something sooner? Webhooks and the API let you build it yourself.