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

# workflows actions list

> Dump the full Clay action catalog as greppable JSON.

Dump the Clay action catalog — the building blocks for a workflow node's `tools`. The catalog is large (\~1.5k entries), so the intended flow is dump-then-filter: write it to a file once, then grep or `jq` it repeatedly.

To use an action in a node's tools, take its `packageId` and `actionKey` (or reuse a `configuredTools[].toolId`). The catalog carries no input field names — before binding any input, fetch them with [`clay workflows actions schema`](/cli/reference/workflows-actions-schema) and use the exact names it returns; never guess input names from an action's name or outputs.

These are workflow building blocks, not function tools. For function and workflow routines, see [`clay routines list`](/cli/reference/routines-list).

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
clay workflows actions list
```

## Output

Each action carries its full documented field set so the catalog stays greppable. Fields are present only when the catalog supplies them.

```json theme={"theme":{"light":"github-light","dark":"github-dark"}}
{
  "data": [
    {
      "type": "action",
      "actionKey": "find-email-from-name",
      "functionId": "fn_123",
      "name": "Find email from name",
      "displayName": "Find email from name",
      "description": "Look up a work email from a name and company.",
      "packageId": "56058efe-4757-4fe7-a44b-39c2d730c47a",
      "packageDisplayName": "Email finder",
      "categories": ["enrichment"],
      "creditCost": 1,
      "outputParameters": [],
      "priorityTier": 1
    }
  ]
}
```

| Field              | Type            | Description                                                                                      |
| ------------------ | --------------- | ------------------------------------------------------------------------------------------------ |
| `data`             | array of object | The action catalog. Each entry is one action.                                                    |
| `data[].packageId` | string          | Package id. Pass to `workflows actions schema` and use when adding the action to a node's tools. |
| `data[].actionKey` | string          | Action key. Pass to `workflows actions schema` and use when adding the action to a node's tools. |

Each action also includes, when supplied by the catalog: `type`, `functionId`, `name`, `displayName`, `description`, `packageDisplayName`, `packageDescription`, `documentationUri`, `categories`, `actionLabels`, `creditCost`, `usesPrivateKeyCost`, `paymentType`, `outputParameters`, `dataStrengths`, `whyUseful`, `useCaseExamples`, `providerDescription`, `clayUseCase`, `configuredTools`, `availableAppAccounts`, and `priorityTier` (lower ranks higher).

## Errors

| Code             | Exit | Notes                                          |
| ---------------- | ---- | ---------------------------------------------- |
| `auth_forbidden` | 3    | The API key lacks permission for this command. |

## Examples

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
clay workflows actions list > catalog.json
jq -r '.data[] | select(.name | test("email";"i")) | "\(.packageId) \(.actionKey)"' catalog.json
clay workflows actions list | jq '.data | length'
```