Skip to content

Connect your tools

Connect Enclessa to GitHub, GitLab, Forgejo or Gitea, post into channels through incoming webhooks and send signed outgoing webhooks. Build automation with slash commands, bot accounts and the REST API, and let apps connect through OAuth2. Members can sign in through your identity provider over SAML or OpenID Connect, with SCIM provisioning. The options below describe the supported connections.

Updated

Built and reachable

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.

Said plainly

What Enclessa does not integrate with

Missing a connector you need? Talk to us before you buy, and we will tell you honestly whether it is plausible. Ask us first.

  • No open app store, and no third-party code insidePartner apps are reviewed by the operator, run on their publisher’s servers and reach an organisation only through OAuth, the API and signed webhooks. Nothing loads or executes inside Enclessa.
  • Single sign-on depends on the planSAML or OpenID Connect and SCIM are in the Enterprise plan. Passkeys and authenticator apps work on every plan.
  • No Slack, Jira, Linear, Asana or Notion connectorAnything else goes through a webhook, a slash command or the API.
  • No Zapier, Make or other automation platform listingYou can call the API from one, but there is no maintained connector.
  • No message content in outgoing eventsOutgoing webhooks carry identifiers and metadata; content is read through the API.
  • No interactive messagesNo buttons, menus, modals or forms. A slash command answers with text.

Bring your team over this afternoon

Free for up to 10 people, with encrypted direct messages and video calls. No payment card, no time limit, no server to run.

For businesses and organisations only — not available to consumers.

Create your organisationCompare plans