Feature Request: Tulip Function Import/Export or Cross-Workspace Availability

Product Suggestions
, , ,
1

Overview

Currently, Tulip Functions (reusable logic components) are workspace-specific and cannot be imported/exported or shared across multiple workspaces within the same Tulip instance. This creates duplication and maintenance challenges for enterprises operating multiple sites under one instance.

Problem Statement

  • No portability: Functions cannot be exported from one workspace and imported into another.

  • Duplication: Teams must recreate the same logic in each workspace, increasing effort and risk of inconsistencies.

  • Enterprise inefficiency: Large organizations need standardized logic (e.g., calculations, validations, connector wrappers) across all sites.

Proposed Enhancement

  1. Import/Export Capability

    • Allow exporting a function as a JSON or Tulip-native package.

    • Enable importing into another workspace with dependency checks (variables, connectors).

    • Provide conflict resolution for naming and versioning.

  2. Cross-Workspace Availability

    • Introduce Global Functions at the instance level:

      • Functions created in one workspace can be marked as Enterprise Functions.

      • Enterprise Functions become read-only or shared across all workspaces.

      • Updates to Enterprise Functions propagate to all linked workspaces with version control.

Benefits

  • Consistency: Standardize logic across all workspaces.

  • Efficiency: Eliminate duplication and manual recreation.

  • Scalability: Easier rollout of global enhancements.

2

Thanks for the post @sagar007 - and also for the other recent feature requests!

Quick note that Functions Import/Export is planned and in flight! We’ll first release individual Function I/E and then I/E of Functions with Apps. The full functionality will be part of Functions GA, currently planned for this sprint. We’re iteratively releasing key Functions features, and I/E is a key item on that list.

By the way, we’d welcome a conversation to go through your full list of feature requests, underlying use cases and priority – and also to share our nearterm roadmap. If this is interesting, please reach out to your Partner Manager to set up!

  • Olga