




Have any questions? We’re here to help You
Connecting to any system through Makini is straightforward. You select the product you want to connect to, log in with your credentials, and receive an API token. The process takes just a few clicks and works consistently across all 2,000+ supported systems. For most systems (85-90% of cases), you only need the instance URL, username, and password. Some systems may require additional steps like API token generation, and we provide detailed authentication guides for these cases. The connection experience is designed to be simple enough that non-technical users can complete it without IT support.
All API requests require authentication via bearer token. After successfully connecting a system through Makini's authentication module, you receive an API token. Include this token in the Authorization header of your requests: `Authorization: Bearer YOUR_API_TOKEN`. Each connection has a unique token, allowing you to manage multiple customer connections independently. Tokens remain valid as long as the underlying system credentials are valid and the connection is active. If a customer changes their system credentials, you'll need to reconnect to obtain a new token.
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.
Makini sends webhooks for several event types: sync completion (successful or failed), connection authentication required (when credentials need renewal), connection status changes (online/offline), and system errors requiring attention. Each webhook payload includes the event type, timestamp, connection ID, and event-specific details like error messages or affected entities. You can configure which events trigger webhooks on a per-connection basis. For workflow-based integrations using Makini Flows, you can also set up custom webhooks triggered by specific conditions in your business logic, providing granular control over real-time notifications.
