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 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.
Output
Each action carries its full documented field set so the catalog stays greppable. Fields are present only when the catalog supplies them.| 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. |
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. |

