








































































































.webp)





















Verizon Connect Fleet is a fleet management platform offering GPS tracking, asset tracking, ELD compliance, and route optimization for commercial fleets.
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.
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.
Design your webhook receiver to handle duplicates and out-of-order webhooks, as network issues or retries can cause both scenarios. Keep the receiver lightweight—ideally writing incoming webhooks to a queue or reliable storage—then process them asynchronously. This prevents timeouts and allows your system to handle high-volume webhook spikes. Respond with a 200 status code immediately after receiving the webhook, before processing begins. Implement idempotency by tracking processed webhook IDs and skipping duplicates. Use constant-time comparison for signature verification to prevent timing attacks. If webhook processing fails, log the error but still return 200 to prevent unnecessary retries. Set up monitoring and alerts for webhook failures so you can investigate issues promptly. For critical workflows, combine webhooks with periodic polling as a fallback mechanism.
If you continue to experience problems with your NetSuite M2M connection after following the troubleshooting steps, contact Makini support at support@makini.io. You can also refer to the NetSuite API Documentation and Makini Documentation for additional technical details.
