Understand about packages.
A package comprises services and associated files, including specifications and document types. Upon project creation, a package is generated with a name identical to that of the project. For instance, creating a project called ProjectAny results in an automatic creation of a corresponding package named ProjectAnyProject within the system.
Apart from your project assets, you can add your own integration packages stored in any external repositories to a project and use it along with other assets in the project. Currently, you can add packages that are stored in GitHub.
For more information about packages, add and manage packages, see Packages.
Any services that are part of the package are known as Package Services. You can access the services in these packages in your integrations as follows:
Workflows
Flow Services
Assume that you have added your own integration packages stored in any external repositories to a project. For more information on how to add packages, see Adding Packages to a Project. Let us see how to use these services in a workflow and configure runtimes for these services.
Go to the project where the services are added.
Click Integrations > Workflows.
Click the 
(plus icon). The workflow page appears.
You can search and filter package services by either their service name or by the package name.
Click Create New Workflow. The workflow canvas appears.
Click Flow Services to view the package services.
Select the package, and drag and drop the package into the canvas. For example, Addint.
Click the Addint package and select Settings.
The AddInt settings dialog box along with the service name appears.
Select a runtime from the Select Integration Runtime drop-down list.
Click Next. The Incoming data page appears.
Add the input values.
Click Next. The Test this action page appears.
Click the Sync button to sync the packages to the runtime.
Click Test.
Click Done.
Assume that you have added your own integration packages stored in any external repositories to a project. For more information on how to add packages, see Adding Packages to a Project. Let us see how to use these services in a flow service and configure runtimes for these services.
Go to the project where the services are added.
Click Integrations > Flow services.
Click the (plus icon). The Flow Editor page appears.
In the flow step, click All > Package Services.
Select a service.
Select an operation.
Select a runtime.
Click 
to sync the packages.
An orange or red dot appears on the Sync button when user actions are required. Hover over the Sync button to view the information.
For more information on scenarios and actions, see Indications for the Sync and Run buttons in Flow Editor.
Click Save. The services are now configured to your runtime.
The Deploy Anywhere page under Projects > Connectors displays services used in packages that you imported into your project and consists of the following sections:
Filters
Connector Table
You can use filters to view the desired package services based on the following options:
Connector: Name of the package service.
Type: Type of package service.
Account: Name of the account used in the package service.
You can use any of these filter options individually or in combination to search for package services.
You can view the list of all connectors that are used in a package. The table lists the following details:
Connector: Name of the package service.
Type: Type of package service.
Account: Name of the account used in the package service.
The Publish wizard does not display the package services if any integrations are using them. If you publish a project all packages added to the project are automatically published, irrespective of whether you have used any package services or not in the integration.
The Deploy wizard includes the Integration Runtimes page allowing you to remap, sync, and restart the runtimes.
The Integration Runtimes page lists all runtimes configured for the services used in the integrations. By default, the runtimes configured in the source environment are considered in the target environment during the first deployment. Otherwise, the most recently configured runtime is considered.
Additionally, you have options to synchronize or restart runtimes after a successful deployment.
Some key points to note for successful deployments are as follows:
Packages added to a project are not deployed if the target tenant does not support deploy anywhere assets.
Packages added to a project are neither exported nor cloned when you export or clone an integration using package services.
While importing or deploying a project using Public APIs,
The new project name provided in the payload is not considered and the same project name that is present in the source environment is used.
You must configure the runtimes in the target environment after a successful deployment.
When importing or exporting a project that includes package services, configuring the runtimes in the target environment is necessary after a successful import.
Before you Begin
Ensure that the GitHub accounts used for adding packages in your source environment are also configured in the target environment.
Ensure that the runtimes required for running package services used in the integrations are configured in the target environment.
Basic Flow
Log in to your tenant (destination).
Go to Projects dashboard. If a new deployment is available for a project, then a message appears on the project card.
Click the project card that has the deployment message. A confirmation messages appears.
Click Yes. The Deployments page appears listing all deployments.
Click Deploy. The Integration Runtimes page in the Deployment wizard appears.
Select the runtime from the Target Integration Runtime drop-down list.
If the integration is already present in this project and has the same package services configured in it, then the runtime is selected based on the current configuration instead of what is present in the deployment.
If the runtime does not exist in the target environment, then an error message appears, and you need to either create a runtime or select a runtime from the existing list.
Do one of the following actions:
Select Sync all the target runtimes on deployment if you do not want to reconfigure the package service connections after deployment. The Restart Options appears.
Clear Sync all the target runtimes on deployment if you need to reconfigure the package services connections after deployment.
Click Restart Options to select specific runtimes that must be restarted after a successful deployment in the Selected target integration runtimes to restart page.
Offline runtimes are not listed in the Selected target integration runtimes to restart page.
Syncing and restarting happens only for the running runtimes.
Cloud runtime cannot be restarted.
The sync and restart operations are asynchronous process and may take additional time even after the project has been deployed.
Click Next. The Accounts page appears. Follow the steps mentioned in the Deploying Projects section from step 5.
Post Deployment Steps
Verify your configurations. For example,
Reconfigure the package service connections, if any.
In REST or SOAP APIs, if you are using flow service containing package services, then you must reconfigure the runtime configurations post deployment. This is because the runtime details selected during the deployment are not retained.
Test and monitor your integrations in the target environment after successful deployment.