Overview:
Currently, Tulip connector functions do not support arrays as input parameters. This limitation creates challenges when integrating Tulip with enterprise systems such as ERP platforms and middleware solutions like MuleSoft. Many real-world use cases require passing multiple values or structured data in a single request, which is not feasible under the current design.
Why This Matters:
Modern integrations often involve batch operations—such as processing multiple orders, updating several records, or transmitting grouped sensor data. Without array support, developers must resort to repetitive API calls or complex workarounds, which increases latency, operational cost, and complexity.
Proposed Enhancement:
Introduce native support for arrays (including JSON arrays) in connector function inputs. This should allow arrays of primitive types (e.g., strings, numbers) and objects, with proper validation and parsing within Tulip.
Benefits of This Feature:
-
Efficiency: Reduces the need for multiple API calls by enabling batch processing in a single request.
-
Scalability: Supports high-volume data transactions, making Tulip more suitable for enterprise-grade workflows.
-
Cost Reduction: Minimizes network overhead and improves performance for integrations with ERP, MES, and IoT systems.
-
Flexibility: Aligns Tulip with modern API standards and integration patterns, improving compatibility with systems like MuleSoft.
Example Use Cases:
-
Sending multiple order IDs to an ERP system for status updates in one call.
-
Transmitting grouped machine data from IoT sensors to Tulip for real-time analytics.
-
Passing multiple items for batch operations in manufacturing workflows.