IntegrationIntegrations

Connect the tools, not the permissions.

Connect the moments where people work already happens.

  • Slack, Linear, incident.io, Telegram, and MCP share one identity model.
  • Every action is rechecked server-side against the linked employee.
  • A connected tool never becomes an accidental authority.
Book a demoExplore Slack
Runtime path
  1. 01Identity
  2. 02Permission check
  3. 03Source record
  4. 04Connected tool

Operational flow

How the connection works in Perelan

Start with identity and setup, then follow the data direction, permission check, source record, and fallback state.

01

Verified connection catalog

Each connection is included because the repository contains a product surface and backend behavior: Slack actions/imports, Linear issue reads, incident.io duty sync, Telegram recruiting intake, and MCP tokens/tools.

SlackLinearincident.ioTelegram
02

Integration principles

Connected identity matters, actions are checked server-side, credentials are handled through the integration service, messages link back to source records, and error states should not broaden access.

03

Workflow examples

A candidate PDF in Slack can become a parsed candidate and authorized decision. A Linear issue can sit beside a goal. incident.io can add duty context. MCP can expose scoped tools to an external AI client.

Runtime path

  1. Identity
  2. Permission check
  3. Source record
  4. Connected tool

Relevant product paths

SlackLinearincident.ioTelegramMCPImplementationSecurity

Controls and boundaries

Does this bypass Perelan permissions?

No. The marketing examples are compressed, but the product path still checks the acting user, role, group scope, and domain permission before data is shown or changed.

Is the page showing real customer data?

No. The product demonstrations use fictional names, roles, dates, and values so the workflow is clear without exposing real people or companies.