Skip to content

Connect Closelly with the way your organization works.

Integrate people, content, channels, data, and processes to reduce manual tasks and create a continuous learning, practice, and management experience.

Closelly adapts to your ecosystem, not the other way around.

Standard capabilities, configuration, project-specific integrations, and custom development.

  • IntegrateConnect Closelly with authorized systems, sources, channels, or destinations.
  • AutomateTurn events and rules into consistent actions, tracking, and reporting.
  • Build to fitDevelop specific applications, portals, experiences, or workflows.
Training and technology professionals reviewing a screen together in an office.

Authorized systems and sources

  • Directories and HRIS
  • Agreed spreadsheets and files
  • Content and catalogs
  • Client management systems
  • Operational events
  • Identity and structure
  • Rules and automation
  • Learning and practice

Channels, reports, and destinations

  • App
  • Web
  • WhatsApp
  • Reports and BI
  • Destination system

Illustrative diagram: five categories on each side, not a catalog of available systems.

Less fragmentation

When systems do not communicate, people end up coordinating them manually.

Person checking statuses and outstanding items on a computer while using a phone.
  • Users uploaded and updated in multiple platforms.
  • Assignments that depend on spreadsheets or emails.
  • Data scattered across systems.
  • Reminders sent manually.
  • Reports assembled repeatedly.
  • Special processes that do not fit a standard LMS.
  • Limited continuity between learning, practice, management, and results.

A good integration does not add technology for its own sake. It eliminates interruptions, errors, and repetitive work in an important process.

Four solution levels

From what already exists to what is built for your process.

  1. Available

    Available as standard

    Capabilities already included or enabled in the platform and its channels, depending on contract and configuration.

  2. Configurable

    Client configuration

    Fields, groups, rules, branding, content, permissions, learning paths, or workflows configured without developing a new integration.

  3. Project-specific

    Project-specific integration

    Connection with an external system through available mechanisms and an agreed technical scope.

  4. Subject to assessment

    Custom development

    An application, portal, automation, or experience designed for a specific need.

Availability, timing, and scope depend on Closelly's capabilities, the third party's APIs or formats, permissions, security, and data quality.

The right person, in the right experience

Keep users, groups, and attributes aligned with your organization.

  • Create, update, or deactivate users.
  • Groups, departments, roles, locations, countries, shifts, or other segments.
  • Assign content or experiences based on rules.
  • Controlled imports and exports.
  • Connect with directories, HRIS, or other authorized sources.
  • Authentication and access through compatible mechanisms.
  • Source traceability and error handling.

We do not promise real-time synchronization or universal SSO. Frequency, direction, and source of truth are defined when specifying each integration.

Example structure

Organization
Head office and subsidiaries
Segment
Sales, operations, field teams
Attributes
Role, location, shift, country
Rule
Joining a group assigns a learning path

This configuration is not available by default.

Learning, content, and results

Connect what is assigned, what happens, and what you need to report.

  • Receive catalogs, content, or assignments.
  • Activate learning paths or experiences based on groups or events.
  • Exchange progress or completion statuses.
  • Send results to reports, BI, or internal systems.
  • Connect evidence or statuses when the project allows it.
  • Incorporate authorized sources into experiences with LENA.
  • Deliver files or exports with an agreed structure.

We do not claim compatibility with SCORM, xAPI, LTI, HR-XML, or other standards without explicit confirmation for the project.

A multichannel experience

Activate the experience where people are.

  • App

    A complete, continuous mobile experience for learning, practice, and tracking.

  • Web

    Browser access to enabled experiences.

  • WhatsApp

    Onboarding, microlearning, communications, re-engagement, or configured experiences.

  • Email and notifications

    Operational support when included in the agreed workflow.

  1. An invitation arrives through WhatsApp or email.
  2. The person practices with LENA in the app.
  3. The responsible person reviews progress on the web.
  4. The result becomes available for reporting.

Each feature depends on the channel and configuration: not all capabilities are identical across the app, web, and WhatsApp.

From an event to an action

Reduce manual work without losing control.

  1. 01Source or eventAn authorized source reports a change.
  2. 02ValidationData, duplicates, and exceptions are checked.
  3. 03RuleThe agreed condition is evaluated.
  4. 04ActionThe assignment, message, or update is executed.
  5. 05ResultThe outcome and its status are recorded.
  6. 06Alert or reportThe responsible person is informed.

Possible examples

  • Add or update users from an agreed source.
  • Assign a learning path when someone joins a group.
  • Send an invitation or reminder.
  • Re-engage an inactive person.
  • Notify a responsible person when a critical condition occurs.
  • Generate or distribute a report.
  • Synchronize a status with an external system.
  • Close or update an activity when an authorized milestone is confirmed.
  • Source of truth
  • Event and frequency
  • Conditions and exceptions
  • Permissions
  • Idempotency or duplicate prevention
  • Retries and error handling
  • Operational owner
  • Traceability and monitoring

Automation is neither magic nor error-free. That is why exceptions, retries, owners, and monitoring are defined.

Less manual chasing for training providers

Closelly helps manage the SENCE declaration-signing process.

  1. Agreed upload or synchronization of participants and course data.
  2. Contact through WhatsApp or email according to the contracted workflow.
  3. Individual link to begin the process.
  4. Simplified mobile experience to review, authenticate, and sign.
  5. Recurring reminders for people with pending signatures.
  6. Status tracking and reporting.
  7. Option to update an activity or status in Moodle when the integration is implemented and validated.
Awaiting contact
The person has not yet started the process.
In progress
They have opened the link and are reviewing the declaration.
Signed
The process has been completed and recorded.
Needs review
Incomplete data or an operational exception.

Example statuses, without personal data or outcome figures.

Small consulting team reviewing training programs for several clients.

This automation is an operational solution from Closelly. It must not be presented as an official API, partnership, or native integration certified by SENCE. Its scope and availability must be confirmed before publication.

When configuration is not enough

We build experiences around a real process.

  • Applications or portals with adapted branding and experiences.
  • Onboarding or special programs.
  • Operational dashboards.
  • Forms and guided workflows.
  • Conversational experiences with LENA.
  • Specific automations.
  • Connections between Closelly and client systems.
  • Solutions for organizations with multiple clients, programs, or countries.
  1. Discovery
  2. Scope
  3. Design
  4. Estimate
  5. Validation
  6. Agreed maintenance

Custom development is not unlimited and is not automatically included in licenses.

Product frame reserved for an application or portal developed with client authorization.

Structural HTML scene: it does not represent an existing application.

For companies, training providers, and consultancies

The same platform, three ways to connect it.

Companies

Connect people, structure, content, channels, and results with their internal ecosystem.

Training providers

Reduce operational workload, manage multiple programs, automate follow-up, and incorporate SENCE or Moodle workflows subject to scope.

AI and data-related integrations

Related capabilities, each with its own scope.

Insights and MCP

Insights helps interpret data and interactions within Closelly. MCP Business lets you query authorized domains from compatible AI clients.

Models and knowledge bases

LENA can use authorized models, content, and sources according to the project's architecture and configuration.

We do not claim universal compatibility with every model, system, or database.

How we assess an integration

First the process. Then the technology.

  1. Define the problem, outcome, and responsible people.
  2. Map systems, data, sources, and destinations.
  3. Review APIs, formats, permissions, frequency, and restrictions.
  4. Agree on architecture, rules, security, and error handling.
  5. Test with controlled data and validate edge cases.
  6. Deploy, monitor, document, and maintain.

Checklist for the initial meeting

  • System you want to connect
  • Workflow objective
  • Input and output data
  • Volume and frequency
  • Users and permissions
  • Available API or documentation
  • Third party's technical owner
  • Dependencies, risks, and success criteria

Categories, not a marketplace

Which type of connection we mean in each case.

  • Subject to assessment

    Identity and people

    Directories, HRIS, or authorized sources of users and attributes.

  • Project-specific

    Content and catalogs

    Receiving content, catalogs, or assignments with an agreed structure.

  • Available

    Contact channels

    App, web, WhatsApp, email, and notifications according to configuration and contract.

  • Project-specific

    Data and reports

    Exports or delivery to reports, BI, or internal systems.

  • Available

    Rules and automation

    Events, conditions, and actions configured within Closelly.

  • Subject to assessment

    Special operational workflows

    Processes specific to training providers, consultancies, or operations with particular requirements.

These categories describe connection types, not ready-made vendor integrations. We do not display third-party logos without current authorization.

Frequently asked questions

Common questions about integration and automation.

Does Closelly integrate with any system?
It depends on the external system's APIs, formats, permissions, restrictions, and technical feasibility.
Do we need to replace our LMS or HRIS?
Not necessarily. Closelly can complement the current ecosystem, depending on the use case.
What is the difference between configuration and integration?
Configuration adapts existing capabilities; an integration exchanges data or actions with another system.
Are integrations included in licenses?
Commercial scope depends on the required capability, configuration, or project and is defined case by case.
Can you develop a custom application?
Yes, after discovery, assessment, estimation, and agreement on maintenance.
Do WhatsApp, app, and web have the same features?
Not necessarily. Each experience depends on the channel and configuration.
Does Closelly have an official SENCE API?
No. Sworn declaration automation is an operational solution from Closelly whose scope is confirmed for each implementation.
Can it integrate with Moodle?
Workflows are assessed or developed by project; the current scope must be confirmed before promising availability.
What happens if the external system changes?
The integration may require adjustments, testing, or maintenance according to the agreement.
How is data protected?
Each project defines access, minimization, exchange, storage, and responsibilities.

Tell us which system or process you need to connect.

We will start with the outcome you want, the systems involved, and technical restrictions to assess a viable solution.

  • We start with the process and expected outcome
  • We review systems, permissions, and technical restrictions
  • We define whether configuration, integration, or development is needed

Assess an integration or automation

Tell us about your challenge in one or two sentences.

If you cannot complete verification, open the scheduler directly. Opening it does not confirm or submit this form.

We use your information only to respond to this request. Privacy policy.