Recipe Lifecycle Management

Overview

Recipe Lifecycle Management (RLCM) allows you to export and import your PlanRadar Connect recipes and their dependencies between Workato workspaces. This is useful when:

• Moving recipes from a development or test workspace to a production workspace

• Sharing a complete integration setup with another team or client

• Backing up your recipes in an external version control system (such as GitHub)

A package exported via RLCM can include recipes, connections (as placeholders), lookup tables, message templates, custom connectors, environment properties, and other dependencies.

Note: RLCM does not export connection credentials. After importing a package, you must reconnect any applications in the target workspace.

Where to Find It

In your Workato account, go to Tools > Recipe lifecycle management in the sidebar navigation.

The interface has two tabs:

• Export — create and manage export manifests

• Import — deploy packages into the current workspace

Exporting Recipes

Exporting works in two steps: first you define a manifest (a list of what to include), then you build and download the package.

1. Create a Manifest

1. In the Export tab, click Create manifest.

2. Enter a name for the manifest.

3. Select the source folder containing the recipes you want to export. Workato automatically detects all recipes and their dependencies within that folder.

4. Review the asset list. Deselect any items you do not want to include.

5. For each lookup table, choose whether to include data (export all rows) or ignore data (export headers only).

6. Save the manifest.

Note: Assets from other folders or projects are not included automatically. If your recipes depend on connections or recipe functions stored elsewhere, move them into the source folder before exporting.

2. Build and Download the Package

1. Open the saved manifest and click Build and export package.

2. Once the build is complete, download the .zip file.

You can reuse the same manifest for future exports. Workato will flag any changes (new assets, edited recipes, deleted items) for review before each re-export.

Importing Recipes (Deployment)

1. In the Import tab, drag and drop the .zip package file or click upload from device.

2. Select a target folder in the current workspace. The folder must already exist, or select New project to create one.

3. Click Next. Workato reads the package and shows a preview of what will be created or overwritten.

4. Review the import status for each asset:
   Creates a new recipe — recipe does not yet exist in the target folder
   Overwrites recipe — an existing recipe with the same name will be replaced
   No change — the recipe is identical to the existing version

5. Confirm the import.

After import, reconnect any applications that require authentication. Running recipes that were overwritten are automatically stopped and restarted.

Note: The maximum package size for import is 100 MB.

Lookup Tables on Import

For each lookup table in the package, choose:

• Overwrite — replaces all existing data in the table

• Ignore data — imports the table structure (column names) only, leaving existing data intact

Tips

• Organise recipes into folders before exporting. Workato exports assets at the folder level, and connections should be in the same folder as the recipes that use them.

• Use consistent folder names across workspaces (development, test, production) to make imports predictable.

• Reuse manifests when re-exporting updated recipes — you do not need to create a new manifest each time.

• Delete manifests you no longer need to prevent unintended access to their contents by other workspace members.