> 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/use-a-hyperflow-from-autom-store.md).

# Use a Hyperflow from Autom Store

Use the Hyper Flow Store under Catalog to find a reusable Hyperflow or bot, review its setup requirements, and add it to your environment. Older versions may label this area Autom Store.

## Before you start

* Have permission to download and configure store content.
* Choose a test environment or an editable copy for initial setup.
* Know the applications, credentials, and runtime access required by the intended process.
* Check any package-specific terms and prerequisites before use.

## Find and review a package

1. Open **Autom Store** from the catalog/store area available in your environment.
2. Browse or search for a relevant process.
3. Open the package's details.
4. Read its description, version information, and setup instructions.
5. Identify the external applications, required inputs, and expected outputs.

A matching title is only a starting point. Review the actual actions and destinations before connecting a package to business systems.

<figure><img src="https://3857940684-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJcSHU5jP5GABQrGmWvW2%2Fuploads%2FUDPDDugWHQyL7BBOTq2u%2Fhyperflow-store-package-setup.jpg?alt=media" alt="Current Teams Proactive Notification Bot package details, version 1.0.0, with Setup selected. Get Hyper Flow was not clicked; this is a package review, not an import or a working Teams connection."><figcaption><p>Current Teams Proactive Notification Bot package details, version 1.0.0, with Setup selected. Get Hyper Flow was not clicked; this is a package review, not an import or a working Teams connection.</p></figcaption></figure>

This package’s Setup tab lists client\_id, client\_secret, teams\_app\_id and user\_mail, plus the required Teams/OAuth connection. These are prerequisites to supply through approved configuration. The visible names are setup instructions, not credentials populated by downloading the package.

Read Description, Benefits, Setup and Guide for the selected version before Get Hyper Flow. Confirm the package’s external application requirements with the current provider setup, then review the imported actions in an isolated test copy.

## Download and configure

1. Select Get Hyper Flow on the current package details after reviewing the setup. Older versions may label the control Download.
2. Follow the setup instructions displayed for that package.
3. Open the downloaded item in your environment. Some versions label this area **Downloaded Automs** under **My Environment > Automs**.
4. Review every credential reference, URL, identifier, file path, and trigger.
5. Replace sample values with values for the intended test environment.
6. Save the editable Hyperflow.

Downloading a package does not complete its external application setup.

## Validate before use

1. Run a small controlled example.
2. Inspect the action inputs and outputs.
3. Confirm the result in the affected application where relevant.
4. Check the error path and any notification behavior.
5. Review the version and trigger before making the Hyperflow available to business callers.

## Expected result

The downloaded Hyperflow is configured for your environment and completes the intended test with the expected outputs.

## Maintain the package

Record the package version and your local changes. When an update is available, compare it with your configured version and test the update before replacing a working flow.

## Troubleshoot

* Package missing: check the selected environment, download result, and account permissions.
* Action unavailable: install or activate the required library version.
* Authentication fails: select the appropriate app credential and verify its access.
* Sample destination is used: inspect the downloaded configuration before another run.
* Result differs from the package description: compare its required inputs, dependencies, and setup instructions with your configuration.

### Review the package before its first run

Treat the first imported Hyperflow as a configuration review. The following sequence produces an understood test draft before connecting a package to business systems.

1\. Open the selected package details and record its title/version. List the applications, credentials, input fields and expected outputs it requires.

2\. Download the approved item and locate the imported draft. Compare its actions with the package description.

3\. Follow the path from trigger to final action. Check every target URL, identifier, file path, credential reference and notification recipient. Replace sample destinations only with approved test values.

4\. If a required app or credential is missing, stop at that dependency and use the corresponding setup guide. Downloading the package does not complete provider onboarding.

5\. Choose one narrow test input and write the expected result before running. After the controlled run, inspect the action values and verify any target-system change. Keep your local edits with the imported package version.

[Install and manage app libraries](/userguide/integrations-and-api/install-and-manage-app-libraries.md)

[Manage app and custom credentials](/userguide/integrations-and-api/manage-app-and-custom-credentials.md)