




Have any questions? We’re here to help You
Makini Flows is our embedded workflow automation platform, built on n8n, which we consider the best workflow automation tool available. It's fully integrated into Makini and runs on our infrastructure. Flows allows you to build complex integration logic using a visual workflow builder—no code required, though code is supported for advanced use cases. Workflows can be triggered by schedules, webhooks, API calls, or events from connected systems. You can perform data transformations, implement conditional logic, call external APIs, and orchestrate multi-step processes. Flows includes over 1,000 pre-built connectors beyond Makini's industrial systems, enabling integrations with databases, messaging platforms, cloud services, and more. Most customer activations are completed using Flows due to its flexibility and ease of use.
Testing should cover authentication, data retrieval, data writing, error handling, and workflow logic. Start by connecting a test system through Makini's authentication flow. Use sandbox or non-production instances of your target systems when available. Test API calls for each entity type you'll use (purchase orders, work orders, etc.) to verify data mapping and field coverage. Test error scenarios by providing invalid inputs or attempting operations without proper permissions. For workflow-based integrations, test each workflow step independently before testing end-to-end. Verify webhook delivery and signature verification. Test with realistic data volumes to identify performance issues. Include tests for connection failure scenarios and verify your error handling and retry logic work correctly.
Makini provides several debugging tools. The dashboard shows detailed request logs including request/response payloads, headers, status codes, and timing. Each API request generates a unique request ID included in responses—provide this when contacting support for faster investigation. For workflow-based integrations, Makini Flows includes execution logs showing each step's input/output, timing, and any errors. Connection health monitoring shows sync history, error rates, and connection status over time. API responses include detailed error information with error codes and messages. For development, we recommend using API clients like Postman or Insomnia to interactively test API calls and inspect responses. Our API documentation includes request/response examples for all endpoints.
Makini maintains API stability and provides advance notice of breaking changes. The current API version is v1. When we introduce breaking changes, we release a new API version while maintaining the previous version for a transition period (typically 12 months minimum). Non-breaking changes (like adding new fields or endpoints) are introduced into the current version without requiring updates. We announce upcoming version changes through multiple channels: email notifications, dashboard announcements, and release notes. API responses include version information in headers. We recommend specifying the API version explicitly in your requests to ensure consistent behavior. During version transitions, we provide migration guides and support for updating integrations.
