
























































































Date/Time node handles date parsing, formatting, timezone conversion, and scheduling logic for workflows, enabling consistent handling of time-based data and automated time-driven actions.
Have any questions? We’re here to help You
Some editions of Date & Time 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 Date & Time that lets you read and write Date & Time data, even for legacy or on-prem instances. You build against Makini once instead of integrating with Date & Time directly.
You integrate Date & Time through Makini's Unified API. Authenticate once and Makini normalizes Date & Time data into a single consistent schema you can read from and write to inside your product. The same connection reaches Date & Time 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 Date & Time's core records as normalized, standardized resources, in both directions: pull data out of Date & Time and push updates back in. Every field is mapped to a consistent Makini schema, so you work with the same object model across Date & Time and every other connected system.
Days, not quarters. Because Makini already builds and maintains the Date & Time connector, you do not reverse-engineer the integration yourself: you authenticate and start reading and writing Date & Time data through the Unified API, typically within a few days. A Date & Time integration built in-house usually takes months plus ongoing maintenance.
Yes. Makini connects to Date & Time over encrypted connections on SOC 2 Type II certified infrastructure, and handles Date & Time 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 Date & Time and every other connected system.
Makini owns the maintenance. When Date & Time 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 Date & Time upkeep stays off your roadmap.
