WhatsApp +1 844 686 2721 24/7
Sign up free
External connections

Connect external signals without exposing credentials.

Configure GitHub, WHMCS, SMS and identity mappings with encrypted credentials and per-company connection status.

Sign up free
AES-256-GCM secrets Masked previews Identity reconciliation
Integrations workspaceLive
Connection hub

Integrations

without exposing credentials.Configure GitHub, WHMCS, SMS and identity mappings with encrypted credentials and per-company connection status.
Ready
04Integration areas
01Admin hub
00Secrets logged
Workflow snapshotView all

01Configure providerIntegrations process stepActive

02Store secretIntegrations process stepActive

03Poll serviceIntegrations process stepActive

Built aroundAES-256-GCM secretsMasked previewsIdentity reconciliation
THE FOUNDATION

Integrations workflows that stay connected.

Configure GitHub, WHMCS, SMS and identity mappings with encrypted credentials and per-company connection status.

  1. Connection settings

    Each integration has its own configured or not-configured status in the admin hub.

    01

  2. Credential security

    Secrets are encrypted, decrypted only in memory and never returned to the client.

    02

  3. Identity linking

    External GitHub and WHMCS identities map back to employees before events can score.

    03
BUILT FOR CONTROL

Details that make integrations dependable.

Encrypted credentials

GitHub and WHMCS secrets use authenticated encryption; AI scoring keys are managed by the platform operator.

Masked client output

The UI only shows safe previews rather than raw secrets.

Secret preservation

Leaving a secret field empty keeps the existing encrypted value untouched.

Biometric devices

Attendance devices connect as a plan-based integration with scheduled punch sync.

Scheduled polling

Background jobs keep external signals fresh.

Holiday and billing services

Public-holiday suggestions and card billing run on operator-managed services — nothing for the company to configure.

WORKFLOW LIFECYCLE

The integration module stages signals for other modules.

It owns configuration, credentials, polling and reconciliation, while consuming logic such as performance scoring lives in the destination module.

  1. 01Configure providerReady
  2. 02Store secretReady
  3. 03Poll serviceReady
  4. 04Link identityReady
  5. 05Feed consumerDone
CONTROL SURFACE

Each integration has a defined purpose.

Every view stays structured and reviewable — nothing hides behind a tab.

Identity

Identity reconciliation

External GitHub and WHMCS identities are mapped back to employees before any event can score.

  • Used byPerformance
  • MappingPer employee
  • UnlinkedHeld

GitHub

Code contribution signals

Poll pull request reviews and merges from selected repositories.

  • Used byPerformance
  • IdentityGitHub login
  • SignalPR activity

WHMCS

Support desk signals

Poll ticket response metrics and quality inputs.

  • Used byPerformance
  • IdentityAgent link
  • SignalTickets

SMS

Gateway config

SMS gateway settings support OTP and notifications.

  • ProviderInfobip
  • Used bySystem admin
  • SecretMasked
CONNECTED BY DESIGN

Integrations works with the rest of HRM.

  • Performance
  • System Administration
  • Employees
  • Notifications
  • Dashboard
COMMON QUESTIONS

What HR teams usually ask about integrations.

No. It stages connection data and signals; the Performance module consumes them.

No. Secrets are never logged, and never displayed again once saved.

External events only score when the GitHub or WHMCS identity is reconciled to an employee.

Operentra HRM / Integrations

See how integrations fits your HR operation.

Map your current workflow to the right HRM setup, permissions and rollout plan.