You can install a Marketplace integration app in any environment in your account — Production or non-production — using a single license. This article is for account owners, administrators, and integration builders. It covers how integration app licensing works across environments, how to install an integration app into a specific environment, and how to test an integration app safely before it goes live in Production. For what environments are, see Multiple environments overview.
Prerequisites: Access to the environment you want to install into, and a purchased integration app license.
Integration app licensing across environments
You don't need a separate integration app license for each environment or installation. Purchase one integration app license, and you can install it in any or all of your environments. You're charged by the number of enabled integration app flows across your account, not by the number of installations or environments.
Global connector licenses also carry across environments. A global license can be used in more than one environment at a time, and its expiration date is tied to your integrator.io account, not to a single environment.
If your account hasn't upgraded to the multiple-environment structure, you're on the legacy Production and Sandbox model, where the two environments share underlying resources instead of keeping them isolated. See Legacy Production and Sandbox accounts for how that affects your resources, and Upgrade to the multiple-environment structure to move your Sandbox to a fully isolated environment. During the upgrade, integration apps keep their status, and partially installed templates and integration apps keep their progress.
Install an integration app in a specific environment
- In the top bar of integrator.io, select Environment, and then select the environment to install into. See Switch between environments.
- Go to Marketplace.
- Open the integration app, and follow the steps to install it.
Best practices for testing in non-production environments
Test an integration app in a non-production environment and validate its configuration before you install it in Production.
- Connect the non-production integration app to the corresponding sandbox or test instances of the apps it integrates with — for example, NetSuite, Salesforce, or Shopify.
- Test flows and field mappings in the non-production environment, and compare the configuration with Production before you turn on flows in Production, to confirm that mappings and request bodies are accurate.
- After your integration app is live in Production, test further changes in a non-production environment first, and then move them to Production. See Clone integrations and resources.
- For NetSuite sandbox accounts, NetSuite doesn't allow app developers (including Celigo) to push updates to SuiteBundles or SuiteApps. Upgrade the bundles in your NetSuite sandbox account yourself so that your integration app stays on the latest version. Otherwise, Celigo can't keep your integration app updated.
- Multiple NetSuite sandbox instances count as a single endpoint, even if you have several connections to the same NetSuite account with different tokens and permissions. This rule doesn't apply to every app: for generic connectors such as the REST API connector, different URIs count as separate endpoints even if they belong to the same app.
FAQ
Do I need a non-production environment to connect to a NetSuite sandbox account?
Not necessarily. If you're building a custom integration, you can create an integrator.io connection to a NetSuite sandbox account from any environment — set the Environment setting on the NetSuite connection. This applies to any application, not only NetSuite.
Note: Although you can connect a NetSuite sandbox account to your Production environment using an integration app license, Celigo recommends installing the integration app in a non-production environment instead, so that you test entirely within sandbox environments. If you use your Production installation to connect to a NetSuite sandbox account, you must uninstall the integration app when testing is done, and then reinstall and reconfigure it to connect to your NetSuite production account.
Can I change my Shopify - NetSuite integration app from a sandbox instance to a production instance?
Yes. If your Shopify - NetSuite integration app has multiple stores, you can clone it from the sandbox instance to the production instance. See Clone integration app flows with the template utility.
Can I switch a connection within an integration app from a sandbox instance to a production instance?
No. This isn't supported in most cases, and Celigo doesn't recommend attempting it. Integration apps depend on the specific app instance they connect to, so switching endpoints or accounts can affect the stability of the integration app.
The one exception is switching a connection to a different user within the same company (for example, from one employee's login to a shared service account). Switching a connection to a different instance of the same app (a different Shopify store, NetSuite account, or Salesforce org) isn't supported.
To move to a new instance, obtain a new integration app license, or ask Celigo support to uninstall the integration app so that your existing license is free for the new instance.