In CloudRadial AutomationAI, extensions are updated over time as vendors change their APIs and as tools are added or fixed. This article covers how to tell when a newer version of an extension is available and how to move your workspace onto it, for both catalog and custom extensions. It is for the Admin and Owner roles.
We'll follow three main steps:
- Checking for a Newer Version
- Updating a Catalog Extension
- Updating a Custom Extension
Step 1: Checking for a Newer Version
Why are we doing this? The Installed tab does not flag updates, so comparing versions is how you find extensions that are behind the catalog.
AutomationAI shows extension versions in two places:
- Installed: each Marketplace row shows the version recorded when you installed it
- Browse: each card and its detail panel show the current published version, and the detail panel also shows the Last updated date
Open Extensions and select the Installed tab. Note the version on the extension's row. Then select the Browse tab and select the same extension's card to open its detail panel. If the version in the detail panel is higher than the version on the Installed tab, a newer version is available. For example, an extension installed at v1.0.0 with v1.1.0 in the catalog is one version behind.
While the detail panel is open, review Required Secrets. A newer version can add or rename secrets, and those secrets must be in your runner Key Vault before the new tools will work.
Step 2: Updating a Catalog Extension
Why are we doing this? Catalog extensions do not update in place, so removing the installed version and installing the current one moves your workspace onto the latest tools.
Note: Removing an extension does not change your runner Key Vault or its secrets. Workflow nodes stay connected to the extension when you reinstall it, as long as the extension's name does not change. A renamed extension is treated as a different extension.
Open Extensions and select the Installed tab. Select Remove on the extension's row and confirm. Then select the Browse tab, find the extension and select Install on its card or in its detail panel.
Return to the Installed tab and confirm the row shows the new version. If Step 1 showed new or renamed secrets, add them to your runner Key Vault.
If the extension comes in both a full and a read-only version, update only the one you have installed. We recommend installing only one version of each extension.
Step 3: Updating a Custom Extension
Why are we doing this? Custom extensions are authored in your own workspace, so you update them by replacing their definition rather than reinstalling from the catalog.
Important -> AutomationAI can only see one version of an extension. If the catalog version is installed alongside your custom version, the catalog version overrides the custom one. Remove the catalog version on the Installed tab before you use a custom version of the same extension.
You can update a custom extension with AI Generate or by uploading an edited definition. Either way, keep the extension's name the same. Workflow nodes stay connected to the extension only while its name is unchanged, and a new name creates a different extension.
Open Extensions and select the Custom tab. Each custom extension row has AI Generate from this…, Download and Delete.
To update with AI Generate, select AI Generate from this… on the extension's row. The AI Generate Extension panel opens with the extension already selected under Start from. In App or service name, remove "(copy)" so the name matches the original exactly. Optionally add links under Documentation link(s), describe the update under What should change, then select AI Generate.
To update by hand, select Download on the extension's row to save its definition as YAML, then edit it locally and keep the slug the same. In the AI Generate Extension panel, expand Author manually or import a .yml and select Upload .yml. Uploads replace an existing extension with the same slug, so AutomationAI asks you to review and confirm the replacement. If the file is rejected, the panel shows the reason. Fix the definition and upload it again.
When AI Generate finishes or the upload completes, the extension's detail panel opens so you can check its skills and tools. The updated definition is active for your runners as soon as it is saved, with no separate install step.
Runner Version Requirements
Some extension features need a minimum runner version. The OAuth settings tokenParams and tokenBodyFormat require runner version 2.5.0 or later. Earlier runners ignore them, and the service will usually reject the token request.
Runners on version 2.0 or later update themselves unless they are pinned, set to manual updates or outside their update window. To check a runner's version, open Runners. If the runner is behind, select Update now.
Next: With the extension updated, test its tools in the AI Playground before running workflows that use it.
If you are still having trouble, we're here to help! Submit a ticket here and check our status page for any service interruptions.
Comments
0 comments
Article is closed for comments.