> For the complete documentation index, see [llms.txt](https://docs.unskript.com/unskript-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unskript.com/unskript-documentation/runbooks/xrunbooks/connecting-actions.md). # Connecting Actions Connecting Actions to build on one another unleashes the full power of your RunBook With a single Action, your xRunBook can be a powerful tool. But to unleash the full potential of unSkript, we can connect multiple Actions. We do this by placing the output of an Action into a variable, and accessing this variable in subsequent Actions. Each Action can have it's output saved into a variable for later use. In this example the List of IAM users is saved in the List `users`:

### Example: {% embed url="" %} Our first step is to get a list of all the IAM users in our AWS account. Drag the "List all IAM Users" Action to your RunBook.

Next, we'll configure this action with credentials (to access our AWS account). There are no required inputs for this action, but let's name the output of the Action "users."

Configuring the Credentials and output of the Action

When we run this Action, the list of users will be saved in the List `users`.

A partial listing of the users in the list.

We can now use the data in `users` to build on our RunBook. In step 2, we'll add a simple Action to the Runbook by clicking `+ Add -> + Action` in the top navigation.

This code loops through all of the users, and creates another list of the users with "doug" in the name. Finally, let's send a message to Slack:

This Action takes the list of doug\_users, finds the length of the list and sends a message to the "devrel\_doug\_test1" channel announcing the number of users.

By naming the output of our Action, we can use that variable in subsequent Actions to manipulate the data, and complete further tasks. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.unskript.com/unskript-documentation/runbooks/xrunbooks/connecting-actions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.