We’re excited to announce the launch of our new design system, for the Celigo platform — a significant step forward in improving usability, consistency, and overall user experience.
-
Modernized user interface: A refreshed look and feel with updated colors, typography, spacing, and components for a cleaner, more intuitive interface.
-
Improved accessibility: Enhanced color contrast, keyboard navigation, and screen reader support to better serve all users.
-
Consistent experience: Unified design patterns across pages and components to reduce friction and increase intuitive usability.
-
Responsive design enhancements: Optimized layouts for a better experience across screen sizes.
Have feedback or questions? Share them on our community forum Celigo Connective. We’d love to hear what you think!
Everyone who signs up to the Celigo platform after this release will automatically be working in the new builder UI. Defaulting to the latest intuitive visual features will quickly get you up to speed building flows and APIs. You can always switch to the old UI, if preferred, until it is deprecated.
You now have more flexibility to work with lookup caches across the platform. Use scripts (including flow hooks) to read from and update lookup cache data as part of your flows. Supported operations include inserting, updating, retrieving, and deleting entries—giving you powerful ways to interact with lookup cache data programmatically.
You can now reference lookup caches as part of ILM, giving you better governance and version control for the flows that use them. References are preserved across snapshots, reverts, pulls, and merges—while the cache data itself remains live and unchanged.
Warning
The data in a lookup cache is not available in Integration Lifecycle Management (ILM). Although references to the lookup cache are included (like in mappings and transformations), ILM does not store or manage lookup cache entries. Learn more about managing lookup caches in ILM.
You can now reference lookup caches in API Builder, just like in flows. This allows you to use in-memory lookups to map data, for example, linking item IDs between your ERP and web stores in an inventory management API. Additionally, you can store environment-specific variables in a lookup cache and reuse them across APIs in different environments, simplifying deployment and reducing errors. This update makes your APIs more flexible, efficient, and environment-aware.
We’ve enhanced the AFEs with line numbers and expand/collapse functionality to improve your data navigation experience. Line numbers make it easier to identify and reference specific parts of complex payloads (especially during troubleshooting or team collaboration). You can also reduce visual clutter by collapsing or expanding sections of hierarchically structured data. These improvements make debugging and validation more efficient.
The new API builder UI is here! Following the launch of the new Flow builder UI, we revamped the API Builder for a more streamlined, intuitive experience. Now you can build APIs quickly and efficiently with a cleaner layout, including:
-
Redesigned interface: A sleek, modern look makes navigation smoother and more intuitive.
-
Improved menu: Quickly access tools and actions with a simplified, organized layout.
-
Refined icons: Enjoy a consistent, polished design that minimizes clutter and improves clarity.
Switch between the new and old interfaces whenever you like - your work stays intact.
We’ve removed the Developer Mode toggle to simplify the platform and reduce confusion. Advanced features like API Builder, scripts, settings, stacks, and APIs are now always visible and accessible to all users — no extra setup required.
The Workday connector now offers access to SOAP APIs via SQL queries. This update allows you to use Workday's SOAP-based services, for dynamic and customizable SQL data retrieval options.
Use plain English to automatically generate Workday SQL queries. For example, type "Show me all open job requisitions in the Sales department", and the Workday connector instantly translates your request into precise Workday queries. You can review and refine these queries using the Build SQL query editor, which offers typeahead suggestions and a preview of the generated SQL statement. Benefits include:
-
Empowered Workday users: Non-technical users can now easily access Workday data.
-
Faster insights: Find immediate answers to questions.
-
Improved accuracy: Review and refine queries with the query editor to minimize errors.
Note
The Celigo platform now supports two versions of the Workday app: an HTTP-based connector and a SQL-based connector. To improve clarity, the HTTP-based version will be referred to as Workday HTTP, while the SQL-based version will retain the name Workday.
We’ve introduced advanced concurrency management settings to the Amazon S3 connector for enhanced performance tuning and rate-limit resilience. You can now configure the target concurrency level to optimize throughput, and view the current concurrency level for better visibility. A new Borrow concurrency from option allows you to share concurrency pools across connections. Additionally, we’ve added an Auto-recover rate limit errors toggle to automatically retry operations when rate-limiting issues are detected. These updates provide greater flexibility and stability when handling large volumes of data with S3.
The Microsoft Active Directory connector now provides a simple view alongside the existing SQL view for export queries.
You can now choose between:
-
SQL view for advanced users who prefer writing queries manually.
-
Simple view for users who want a faster, easier way to build queries visually, without writing any SQL or code. Benefits of the simple view include:
-
Faster query creation using a visual builder that simplifies filtering
-
No technical expertise required, easily select columns and define conditions
-
Support for all standard boolean operators (AND, OR, NOT) for powerful filtering logic
-
Greater accessibility for both technical and non-technical users
-
-
In some accounts, branched flows with an FTP import were stuck in processing
-
Applying branching to lookup records could unexpectedly remove arrays from the data
New articles:
Updated articles: