




Limble is a modern CMMS/EAM platform offering work-order management, preventive maintenance scheduling, asset tracking, spare-parts inventory and mobile access. It’s valued for its intuitive UI and flexible configuration, making it popular with maintenance teams seeking to streamline operations and reduce downtime.
Have any questions? We’re here to help You
Makini supports over 2,000 industrial systems across ERP, CMMS, and WMS categories. This includes major platforms like SAP (ECC, S4/HANA, Business One), Oracle NetSuite, Microsoft Dynamics, IBM Maximo, and specialized industrial systems. We support both cloud-based and on-premises installations. If you need to connect to a system we don't currently support, we're committed to building that integration for you at no additional charge—most new integrations are completed within one business day. You can view our full list of supported systems at makini.io/integrations.
Makini maintains a comprehensive data model built from analyzing thousands of industrial systems. When data flows through Makini, we automatically transform it from the source system's format into our standardized structure. For example, purchase orders from SAP, NetSuite, and Dynamics all return with consistent field names, data types, and structures. This normalization happens in real-time as data passes through the API. You also have access to raw data if needed for specific use cases. The unified model covers common entities like purchase orders, work orders, inventory items, vendors, and assets, with extensive field coverage across systems.
Yes, you can trigger syncs manually through both the API and the Makini dashboard. The API provides endpoints to initiate syncs for specific entities (purchase orders, work orders, etc.) on a given connection. Manual syncs are useful when you need immediate data updates outside the regular schedule, when onboarding new customers, or when recovering from sync failures. Manual syncs follow the same incremental logic as scheduled syncs, retrieving only changed records since the last successful sync. You can also trigger full re-syncs that ignore the last sync timestamp and retrieve all records within the configured historical period.
Webhooks allow Makini to notify your application of events in real-time. To set up webhooks, configure a webhook URL in your connection settings or during the initial connection flow. Your webhook endpoint must accept POST requests, respond within 10 seconds with a 200 status code, and use HTTPS with a valid SSL certificate. Makini will send webhook payloads to your endpoint when configured events occur, such as sync completion, connection status changes, or errors requiring attention. We recommend keeping your webhook receiver lightweight—ideally just writing the payload to a queue for asynchronous processing—to avoid timeouts and ensure reliable delivery.
