# Feature Request: Multi-Environment Connector Function Binding Across Apps

**URL:** <https://community.tulip.co/t/feature-request-multi-environment-connector-function-binding-across-apps/15979>\
**Category:** Product Suggestions\
**Tags:** connectors, apps, feature-request\
**Created:** [December 24, 2025, 6:23pm UTC](https://community.tulip.co/t/feature-request-multi-environment-connector-function-binding-across-apps/15979 "2025-12-24T18:23:58Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![sagar007](https://avatars.discourse-cdn.com/v4/letter/s/6f9a4e/32.png) [@sagar007](https://community.tulip.co/u/sagar007)\
**Post date:** [December 24, 2025, 6:23pm UTC](https://community.tulip.co/t/feature-request-multi-environment-connector-function-binding-across-apps/15979/1 "2025-12-24T18:23:58Z")

</div>

**Overview:**  
Tulip currently ties connector functions to a single environment (Production) once an app is published. However, enterprise workflows require **multiple environments** — **Development** , **Pre-Production** , and **Production** —to ensure proper testing, approvals, and controlled releases.

The proposed enhancement is to enable **different published apps** to reuse the same connector while binding to the correct environment.

**App-Level Environment Binding (Core Requirement):**

- Each **published app** should explicitly **bind to an environment profile** (Dev, Pre-Prod, or Prod) at the time of publishing.

- This binding determines which environment configuration of the connector is used at runtime.

- **Example:**

- **Key Points:**

* * *

### **Benefits of App-Level Binding:**

- **Governance & Control:** Prevents accidental use of production endpoints during development or QA.

- **Efficiency:** Eliminates connector duplication and manual reconfiguration.

- **Traceability:** Clear environment association for each app version.

- **Scalability:** Supports enterprise-grade workflows with multiple environments.