> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ideatura.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Shared Automation Library Guide

> Save automations for your team, organise folders, start a chat, run saved work, and copy it to another workspace.

The **Automations** tab is your workspace's shared automation library. Save a useful automation once, give it a name your teammates can recognise, and return to it when the same task comes up again.

This walkthrough uses two example workspaces, **Team Red** and **Team Blue**, and an automation named **Room review checklist**. The names and folders are examples you can replace with your own.

## Find the shared library

Check the workspace name at the top right, then select the **star icon** in the navigation rail to open **Automations**. The library belongs to the selected workspace; switching workspaces changes the collection you see.

<Frame caption="1 — Current workspace. 2 — Automations. 3 — Open in new chat. 4 — Run with params.">
  <img src="https://mintcdn.com/ideatura/h-C-vtRNGYEtSWIb/images/shared-automation-library/02-library-annotated.svg?fit=max&auto=format&n=h-C-vtRNGYEtSWIb&q=85&s=f6349eacd82100eed26441e0bc3c3848" alt="Team Red automation library with the workspace selector, star tab, open-chat button and run button marked in red" width="1170" height="610" data-path="images/shared-automation-library/02-library-annotated.svg" />
</Frame>

Use **Search** to find an automation or folder by name. The sort menu changes the order, and **Collapse all** closes the expanded folders. Expand a folder to see its automations.

An empty library displays **No automations saved in this workspace**. Start by saving an automation from a conversation.

## Save an automation from a conversation

1. In a conversation, ask Ideatura to build the automation you need. Review its purpose and the compiled automation card before sharing it.
2. Open the automation card's **three-dot menu** and choose **Star**.
3. Enter a short, recognisable name, such as **Room review checklist**.
4. Select the destination folder. To create one here, choose **New Folder**, enter its name, and choose **Create**. The new folder becomes the selected destination.
5. Check **Save in**, then choose **Star** to add the automation to the shared library.

<Frame caption="1 — Name the automation. 2 — Select its folder. 3 — Create a folder if needed. 4 — Confirm with Star.">
  <img src="https://mintcdn.com/ideatura/h-C-vtRNGYEtSWIb/images/shared-automation-library/01-save-annotated.svg?fit=max&auto=format&n=h-C-vtRNGYEtSWIb&q=85&s=d8e79982e687b2b259f457f0a01fc1ae" alt="Star automation dialog with Room review checklist named, Room reviews selected, and New Folder and Star controls highlighted" width="920" height="860" data-path="images/shared-automation-library/01-save-annotated.svg" />
</Frame>

Open **Automations** and check that the named item appears in the folder you chose. It is now shared with the workspace, rather than available only in the original conversation.

## Organise automations into folders

Choose **New Folder** in the library toolbar to add a folder. A new library folder initially appears as **New Folder**; use its three-dot menu → **Rename**, enter the name, and confirm with the checkmark.

For a folder inside another folder, open the parent folder's three-dot menu and choose **New subfolder**. Name folders around the tasks your team recognises, such as **Room reviews**, **Drawing checks**, or **Sheet preparation**.

To relocate existing content, use the drag handle that appears beside a row when you point at it:

* Drag an automation into the destination folder.
* Drag a folder into another folder to make it a subfolder.

Expand the destination afterward and check the item is in the intended place. If a search is hiding part of the collection, clear **Search** before arranging folders.

Use a normal folder to organise a collection. **New Chain** is a different action: it creates a sequence of automations intended to run together. See [parameters in automation chains](/automation/automation-parameters/understand-parameters-in-automation-chains) before building a multi-step workflow.

## Start a chat from a saved automation

Choose the **Open in new chat** icon beside the automation, or select the same action from its three-dot menu. Studio creates a new conversation containing the automation card.

<Frame caption="Open in new chat brings the saved automation into a separate conversation. It does not run the automation by itself.">
  <img src="https://mintcdn.com/ideatura/h-C-vtRNGYEtSWIb/images/shared-automation-library/03-new-chat-annotated.svg?fit=max&auto=format&n=h-C-vtRNGYEtSWIb&q=85&s=c86d8c0e2af0e0436673097db06ebf54" alt="A new conversation titled Room review checklist containing the saved automation card, with its title and run control highlighted" width="1060" height="425" data-path="images/shared-automation-library/03-new-chat-annotated.svg" />
</Frame>

Use the composer to discuss or adapt it, for example:

> Adapt this room review checklist for a meeting room. Keep the room-name input and make the accessibility section optional.

Review the newly generated automation before running it. If you want teammates to reuse the revised version, **Star** its new card and deliberately choose its name and library folder. Continuing a chat is not a reason to assume that the shared library entry has been updated.

## Run a saved automation

1. Find the automation in **Automations** and check the application badge beside its name.
2. Confirm the intended application, open document, and access mode. For an automation that changes a Revit model, select the right Revit session and the access needed for that task.
3. Choose the **play icon**. Its menu label is **Run with params** when the automation has parameters, or **Run** when it does not.
4. If a parameter dialog appears, fill the required inputs and review the defaults before choosing **Run**. Parameter controls depend on the automation; some tasks can use their defaults without asking for further input.
5. Follow the new conversation and read the execution report. For model work, inspect the result in the connected application before repeating it on a larger scope.

**Open in new chat** is useful when you want to discuss or change an automation first. **Run** is the shortcut for launching the saved task.

<Note>
  The green checkmark on an automation card indicates successful compilation. It does not indicate a completed run. Check the execution report and the actual result in the connected application.
</Note>

For more detail about inputs, see [run a saved automation with parameters](/automation/automation-basics/run-a-saved-automation-with-parameters).

## Choose how Studio selects an application

Open the **gear icon → Settings → UI** and find **Select App on automation run from Library**.

* **Automatically** uses Studio's application-selection logic and previous selection where available. Check the selected target before running work that changes a model.
* **Ask every time** asks you to select the application session for a library launch. This is useful when you regularly work with several open documents or application instances.

<Frame caption="Settings → UI contains the choice between Automatically and Ask every time.">
  <img src="https://mintcdn.com/ideatura/h-C-vtRNGYEtSWIb/images/shared-automation-library/05-settings-annotated.svg?fit=max&auto=format&n=h-C-vtRNGYEtSWIb&q=85&s=ed45d39766bb1d78d1e9da7b5f96cd46" alt="Application selection setting showing the Automatically and Ask every time options" width="1050" height="350" data-path="images/shared-automation-library/05-settings-annotated.svg" />
</Frame>

Select the option that suits your workflow.

## Control parameter caching

In **Settings → UI**, **Cache automation parameters** has three choices:

| Choice | Behaviour |
| - | - |
| **Always** | Cache parameters by default. |
| **Manual** | Control caching separately for each automation. |
| **Never** | Do not cache parameters. |

<Frame caption="Choose a cache policy under Settings → UI. Manual leaves the decision to individual automations.">
  <img src="https://mintcdn.com/ideatura/h-C-vtRNGYEtSWIb/images/shared-automation-library/06-cache-annotated.svg?fit=max&auto=format&n=h-C-vtRNGYEtSWIb&q=85&s=7a6d395cefa9c5018e26adf2eb41e0c1" alt="Cache automation parameters setting showing Always, Manual, and Never" width="1050" height="335" data-path="images/shared-automation-library/06-cache-annotated.svg" />
</Frame>

For automations whose parameter choices come from the connected model, a **Cache parameters** item can appear in the automation's menu when caching is available. If the parameter dialog offers **Refresh**, use it to reload model-derived choices after the model has changed. Static text and checkbox inputs do not need a list of model choices to be refreshed.

## Copy an automation or folder to another workspace

Copying lets another team reuse a workflow while keeping the source collection in place.

### Copy one automation

1. In the source workspace, open the automation's **three-dot menu**.
2. Under **Copy to**, choose the destination workspace, such as **Team Blue**.
3. Switch to that workspace using the workspace selector at the top right.
4. Open **Automations** and find the copied item. In this example, the individual copy appears at the root of Team Blue's library.

### Copy a folder

1. Open the **folder's** three-dot menu rather than the menu on an automation row.
2. Under **Copy to**, select the destination workspace.
3. Switch to the destination, open **Automations**, and expand the copied folder to check its contents.

<Frame caption="Team Blue after both operations: 1 — A separately copied automation at the root. 2 — The copied Room reviews folder with its automation inside.">
  <img src="https://mintcdn.com/ideatura/h-C-vtRNGYEtSWIb/images/shared-automation-library/04-team-blue-annotated.svg?fit=max&auto=format&n=h-C-vtRNGYEtSWIb&q=85&s=faa0f0b57eaa645de14352e53eaf0ef4" alt="Team Blue library showing an individually copied Room review checklist and a copied Room reviews folder containing the same named automation" width="1170" height="650" data-path="images/shared-automation-library/04-team-blue-annotated.svg" />
</Frame>

Both copies are shown here to make the difference visible; you only need to perform the operation that matches your task. Check the destination's application and document before running a copied automation.

## If something does not look right

| What you see | What to check |
| - | - |
| The saved automation is missing | Check the selected workspace, clear Search, and expand the folder you selected in the Star dialog. |
| The destination is missing under Copy to | Check that your account has access to that workspace. |
| A new chat opens but there is no result | Opening in a new chat does not execute the automation. Use the card's Run control when ready. |
| Parameters cannot be configured, or the report says Not Found | Treat the run as incomplete. Keep the error report and automation name, check workspace access, and [report the problem](/help/problems/report-a-reproducible-ideatura-issue). |
| Model-derived choices look out of date | Use Refresh if available and review the cache policy. |
| The result affects an unexpected document | Stop and check Connected Apps and the library application-selection setting before another run. |

Before handing a workflow to your team, check its name, folder, inputs, intended application, and the result of a small test run.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.