Integrating with Your Tools

HABICUB is designed to sit inside your existing stack rather than beside it. This guide covers what each integration category is actually for, what data crosses the boundary, and the decisions to make before anyone writes a line of configuration.

For which connectors are available today and what a specific one involves, talk to us — scope varies by system and by how your instance of it is configured.

Start with the one that pays for itself

You do not need every integration. In order of return:

Communication — because delivery into the flow of work is the difference between an action being seen and an action being missed.
Identity (SSO) — because it removes the password problem and makes leaver handling correct.
HR system — because it removes ongoing joiner/leaver admin.
Analytics / BI — once you have enough data to want it alongside everything else.
Learning and CRM — genuinely useful, rarely the bottleneck in month one.

Connecting everything before the first cohort has run is the most common way to delay a launch by a quarter and learn nothing in the meantime.

Communication tools

What it is for: delivering MDAs and mentor replies where people already are — Teams, Slack, email, chat.

What crosses: the action content and a link; the person’s identity in that tool.

Decide first: which channel is primary. Two channels for the same action doubles the notification load and halves the attention. Pick one and make the others a fallback.

Watch for: notification fatigue you do not control. If the organization already pushes a lot through the same channel, your delivery timing matters more than usual.

HR systems

What it is for: keeping the population correct without manual CSV work — joiners, leavers, role and manager changes.

What crosses: employee identity, org structure, role, manager, start and end dates. Not performance data, and there is no reason for it to be.

Decide first:

Which direction is authoritative. The HR system should own who exists and who their manager is. HABICUB should own who is on which program. Mixing those produces conflicts nobody can resolve.
What a leaver means. Does their journey stop, or complete? Does their mentor keep the history? Answer this before go-live, not at the first departure.
How often. Nightly is almost always enough. Real-time sync is a lot of engineering for a population that changes weekly.

Watch for: org-structure data that is accurate for payroll and wrong for development. The person someone reports to on paper is not always the person who should see their progress.

Identity and single sign-on

What it is for: one login, correct access, correct offboarding.

What crosses: authentication only — HABICUB does not see or store a password.

Decide first: which claim carries the organization, and how roles map. The common mistake is mapping every HR job title to a HABICUB role; map to the five roles HABICUB actually has and keep the mapping small enough to audit.

Watch for: the offboarding path. This is the question your security review will open with.

Learning platforms

What it is for: connecting existing learning content to the development journey, so an MDA can point at material you already own instead of duplicating it.

What crosses: content references and completion signals.

Decide first: whether learning completion means anything in your program. Usually it should not gate an MDA — that reintroduces exactly the completion-as-proxy problem the journey is designed to avoid.

CRM

What it is for: aligning customer-facing behaviors with what is actually happening in accounts, so a customer-experience program can be targeted rather than generic.

What crosses: account and role context, not customer records.

Decide first: whether you need it at all in phase one. It is the integration most often requested and least often used.

Analytics and BI

What it is for: putting adoption data next to your other people metrics, and running your own analysis rather than only the built-in reports.

What crosses: program, adoption and behavior-change data — exported to your warehouse, where it is yours.

Decide first: grain and retention. Person-level data in a warehouse is a different governance conversation from aggregate data, and it is easier to have that conversation before the pipeline exists.

Before any of it: three questions

Who is the data controller for what? For the platform, your organization is the controller and we are the processor. Write down which fields cross and why — you will need it for your privacy notice regardless of which tools you connect.

What is the minimum field set? Every integration has a default payload that is larger than what is needed. Trim it at design time; removing a field later means a migration and an explanation.

Who gets notified when it breaks? A sync that fails silently produces a population that drifts out of date, which looks like an engagement problem three weeks later.