> For the complete documentation index, see [llms.txt](https://docs.autommate.com/userguide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.autommate.com/userguide/integrations-and-api/install-and-manage-app-libraries.md).

# Install and manage app libraries

Use Library Store, shown as an app store or catalog in some versions, to add a library's predefined actions to your environment and manage the version in use.

## Before you start

* Have permission to activate or update app libraries.
* Identify the app and action required by your Hyperflow.
* Check the library's version information and dependencies.
* Identify flows that already depend on the library before updating it.

## Inspect installed libraries

1. Open the store/catalog area and its **Installed** view.
2. Locate the library.
3. Compare **Active Version** with **Last Version**, where those fields are shown.
4. Open the detail page and review the developer, modification information, and available actions.

An available newer version is not proof that it is compatible with every existing flow.

<figure><img src="https://3857940684-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJcSHU5jP5GABQrGmWvW2%2Fuploads%2F4pGSMxh5gHa6OErTBTX3%2Fapp-store-version-actions.jpg?alt=media" alt="Current catalog detail for the inspected Xurrent library, showing Current Version 3.1.6, Actions (45), and the expanded Create Request entry. No install, activation or update was performed."><figcaption><p>Current catalog detail for the inspected Xurrent library, showing Current Version 3.1.6, Actions (45), and the expanded Create Request entry. No install, activation or update was performed.</p></figcaption></figure>

Use the catalog to verify the selected library version and available action names. The shown Create Request entry contains a short description/configuration summary; it is not the complete request input schema. Open the action in a test Hyperflow to inspect its current required fields and credential selection before implementation.

The Actions, Triggers and Connections tabs describe different parts of the library. Catalog visibility does not prove that a credential is configured or that an action has completed successfully.

## Install or activate a version

1. Locate the app in the available library catalog.
2. Open its details using the row's details/arrow control.
3. Select the intended version from the version selector.
4. Review the actions and their descriptions.
5. Select the available **Activate and Download** control.
6. Confirm the activated version shown by the page.
7. Open a Hyperflow and confirm that the required action is available.

## Configure and test an action

1. Add the required action in the Hyperflow editor.
2. Configure its inputs and output assignment.
3. Select the appropriate application credential.
4. Run a limited test and inspect the result.

The catalog defines which actions the library supplies. You configure an action's inputs in a Hyperflow; this is different from changing the library implementation.

## Manage connections and updates

Review the app's Connections/Connectors area for its available credentials. Maintain credential details in the app/credential management area.

For an update:

1. Record the currently active version and dependent flows.
2. Review the proposed version.
3. Test representative flow paths with the intended version.
4. Activate the approved version and confirm the saved state.
5. Verify the affected flows after the change.

## Expected result

The intended library version is active, its actions are available in the editor, and the selected action works with the configured inputs and credential.

## Troubleshoot

* App absent from the editor: check installation/activation status, selected version, and environment.
* Action differs from a reference example: compare the app/library version and current field definitions.
* Credential absent: check the app selection and the current user's access.
* Flow breaks after an update: inspect the failing action and version change before repeating a business operation.

Keep the selected version with the flow's dependency record so that a future issue can be reproduced.

### Worked check: find the String Assign action in the installed library

Use an already-installed local library to learn the catalog/version path before activating or updating an integration library.

1\. Open the Installed catalog view and find String. Record Active Version and any newer Last Version shown.

2\. Open the library’s detail page and locate Assign in its action list. Review the declared input/output information.

3\. Open a test Hyperflow and locate String → Assign in the action picker. Compare the action and library version with the dependency shown in the editor.

4\. Use the documented request-intake example to configure and inspect one local String result. No library upgrade is needed merely to reproduce a screenshot of an already-installed action.

5\. If the action is absent, check the selected environment and activated version before importing another library copy or changing a production dependency.

[Build a Hyperflow](/userguide/build-automations/build-a-hyperflow.md)

[Use Development Mode and inspect library versions](/userguide/build-automations/development-mode-and-library-insights.md)