Integrations
Five ways in, and an honest list of the ways there are not
Enclessa connects to other systems through five routes: two-way GitHub issue and pull-request sync onto task boards, incoming webhooks that let anything post into a channel, slash commands that call an endpoint you control, bot accounts that are real members with real permissions, and a documented API described by a generated OpenAPI document. There is no app marketplace and no directory of third-party connectors, so what follows is the whole list rather than a selection from it.
Open betaThe platform is being built in the open, so parts of it are not there yet, behaviour changes between releases, and no availability figure is committed while it is in beta. What is still being built.
At a glance
- Connectors that exist
- GitHub, and nothing else
- Open surfaces
- Webhooks in, slash commands out, a scoped HTTP API
- Identity for automation
- Bot accounts inside the normal permission model
- Third-party code
- Nothing loads or runs at runtime
- Marketplace
- None. There is no third-party app catalogue
- Single sign-on
- Not available
What connects to Enclessa today
Each of these is built and reachable now. Each page below says what the capability does, how it works, and what it deliberately does not do.
What Enclessa does not integrate with
Every item here is genuinely absent rather than nearly ready. A platform with a hundred logos on its integrations page usually has four that work, and finding out which four is a job the buyer ends up doing.
No app marketplace and no third-party apps
There is no partner catalogue, no app directory and no submission process. Nothing loads or executes third-party code inside the platform, which is a security position rather than a missing feature. The console does carry a catalogue of first-party modules an operator switches on, and that is a different thing entirely.
No single sign-on
There is no SAML, no OpenID Connect and no SCIM provisioning. Accounts sign in with an email address and a password. If your identity provider is non-negotiable, Enclessa is not usable for you today, and no date is being offered.
No Slack, Jira, Linear, Asana or Notion connector
None of these exists. Anything you want to wire up goes through an incoming webhook, a slash command or the API, which is real work rather than a checkbox.
No Zapier, Make or other automation platform listing
Enclessa is not listed on any integration-platform-as-a-service. You can call the API from one, but there is no maintained connector to pick from a list.
No outgoing webhooks and no event stream
Nothing pushes Enclessa events to an endpoint you run. Integrations that need to know something happened have to ask.
No interactive messages
Messages have no buttons, menus, modals or forms, so an integration cannot open a dialogue inside a message. A slash command answers with text.
If a connector you need is missing, that is a reason to talk to us before you buy rather than a promise that it is coming. We will tell you whether it is plausible, what it would take, and whether anybody else has asked — and if the answer is that you should stay where you are, we would rather say so now than in your second week.
Related
Encrypted collaboration, hosted in Europe.
Create a workspace in a couple of minutes. It is yours at your-team.enclessa.app, hosted in the European Union, with encrypted direct messages from the first one you send.
Open beta. Free plan, no payment card to start.