> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/stackai-tools/workflow-and-catalog-tools/search-stackai-actions.md).

# Search StackAI Actions

Find a action by what it does, its provider, or its tags. Use the results to choose the right capability and learn what it requires.

## Find a action

1. Enter a **Search Query** that describes the operation or event. Add **Provider** to narrow the search to one service.
2. Use **Tags** or **Requires Connection** when they help narrow the results. Leave connection requirements unset to include both authenticated and unauthenticated tools.
3. Enable **Include Parameters** when you need input and output details. Set **Limit** to control how many matches are returned.
4. Read the matched action names, descriptions, and identifiers. Check the required connection and parameters before configuring the selected item.

**Result:** **Actions** contains the matches, with **Total Count** and a **Search Summary**.

## Behavior and troubleshooting

Search finds capabilities; it does not execute an action or grant access to the provider. If a search returns unrelated items, narrow the query or provider. The default result limit is 20, with a maximum of 100.

## Inputs

| Field               | Parameter             | Description                                              |
| ------------------- | --------------------- | -------------------------------------------------------- |
| Search Query        | `query`               | Search actions by name, description, or tags             |
| Provider            | `provider_id`         | Filter to a specific provider                            |
| Tags                | `tags`                | Filter by action tags                                    |
| Requires Connection | `requires_connection` | Filter by connection requirement                         |
| Limit               | `limit`               | Maximum number of results to return Default: `20`.       |
| Include Parameters  | `include_params`      | Include input/output parameter details Default: `false`. |

## Outputs

| Field          | Parameter        | Description                                  |
| -------------- | ---------------- | -------------------------------------------- |
| Actions        | `actions`        | List of matching actions with their metadata |
| Total Count    | `total_count`    | Total number of matching actions             |
| Search Summary | `search_summary` | Natural language summary of search results   |

## Related guidance

[Action Inputs, Outputs, and Validation](https://docs.stackai.com/technical-reference/connections-and-tool-execution/action-inputs-outputs-and-validation.md)


---

# 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.stackai.com/stackai-tools/workflow-and-catalog-tools/search-stackai-actions.md?ask=<question>&goal=<user_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.
