
























































































Function Node enables custom JavaScript code execution within workflows for complex data transformations and logic.
Have any questions? We’re here to help You
Some editions of Function expose an API, but it is often limited, legacy, or inconsistent between versions, and many on-prem deployments have no usable API at all. Makini gives you one modern REST API for Function that lets you read and write Function data, even for legacy or on-prem instances. You build against Makini once instead of integrating with Function directly.
You integrate Function through Makini's Unified API. Authenticate once and Makini normalizes Function data into a single consistent schema you can read from and write to inside your product. The same connection reaches Function plus 2,000+ other ERP, WMS and CMMS systems, so you build one integration instead of one per system.
Through Makini you can read and write Function's core records as normalized, standardized resources, in both directions: pull data out of Function and push updates back in. Every field is mapped to a consistent Makini schema, so you work with the same object model across Function and every other connected system.
Days, not quarters. Because Makini already builds and maintains the Function connector, you do not reverse-engineer the integration yourself: you authenticate and start reading and writing Function data through the Unified API, typically within a few days. A Function integration built in-house usually takes months plus ongoing maintenance.
Yes. Makini connects to Function over encrypted connections on SOC 2 Type II certified infrastructure, and handles Function credentials for you so they are never exposed to your app. You authenticate once, and access runs through Makini's managed, auditable layer. The same security model applies across Function and every other connected system.
Makini owns the maintenance. When Function changes its API, versions, or endpoints, Makini updates the connector, and your integration keeps working with no changes on your side. You get a stable Unified API with webhooks, and Function upkeep stays off your roadmap.
