IntegrationTelegram integrationAvailable

A chat becomes a candidate.

Turn a recruiting conversation into a candidate record.

  • A verified chat sends a PDF or DOCX resume to the bot.
  • It parses the context and tags the source.
  • The candidate lands in the pipeline to continue in Perelan.

Verified integration behavior only. External tools remain their own systems of record where applicable.

Book a demoSee the flow
Runtime path
  1. 01Verify chat
  2. 02Receive resume
  3. 03Parse context
  4. 04Create or match candidate

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

Connect the verified bot

This integration is described through setup ownership, identity mapping, data direction, permission checks, and fallback states so a connected tool does not become an accidental authority.

Plan integration rollout
02

Capture supported candidate fields

This integration is described through setup ownership, identity mapping, data direction, permission checks, and fallback states so a connected tool does not become an accidental authority.

03

Create or match the candidate record

This integration is described through setup ownership, identity mapping, data direction, permission checks, and fallback states so a connected tool does not become an accidental authority.

04

Protect candidate data and bot credentials

This integration is described through setup ownership, identity mapping, data direction, permission checks, and fallback states so a connected tool does not become an accidental authority.

Runtime path

  1. Verify chat
  2. Receive resume
  3. Parse context
  4. Create or match candidate
  5. Continue pipeline

Relevant product paths

Plan integration rolloutRecruitingSlack integrationSecurityImplementation

Controls and boundaries

Can Telegram create a candidate?

Yes, through the verified recruiting intake flow.

Can it import a resume?

The implementation supports PDF and DOCX recruiting documents where configured.

Is the Telegram conversation copied in full?

No broad full-chat archive claim is made. The page describes supported candidate/contact/resume intake only.

Does the bot make hiring decisions?

No. It creates or enriches candidate context for humans to review.

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.