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

# Actions

Explore the B3OS action library and built-in workflow actions.

B3OS actions are typed operations that workflow nodes can execute. Catalog actions and built-in actions share schema validation, typed results, connector requirements, and workflow expressions.

## Catalog Snapshot

The current action library contains 368 actions.

**Action catalog by family**

**Actions**

Action categories and what each family includes.

| Category | Count | What it includes |
| --- | --- | --- |
| Blockchain data | ` 167 ` | Token, market, DEX, DeFi, futures, chain, analytics, and lookup actions |
| EVM onchain | ` 62 ` | Contract calls, token operations, swaps, approvals, wallet-backed transactions |
| Integration | ` 92 ` | Slack, Shopify, Coinbase Business, Google Sheets, Pipedream apps, Firecrawl, Magna, and provider workflows |
| Messaging | ` 3 ` | Notification and messaging actions |
| Social | ` 13 ` | Farcaster, Neynar, Twitter/X, Clanker-style social workflows |
| Solana onchain | ` 7 ` | Solana wallet and transaction actions |
| Utility | ` 22 ` | Format, parsing, lookup, and helper actions |
| Wallet management | ` 2 ` | Organization wallet management surfaces |

**Schemas are the contract**

The app, Caddie, and API use the same public action schemas for titles, descriptions, tags, connector requirements,
  inputs, and outputs.

## Action Anatomy

**Action anatomy**

**Action details**
  **Input schema**
  **Action behavior**
  **Output schema**
  **Workflow policy**
  **describes**
  **validated payload**
  **result**
  **expression data**

| Field           | Meaning                                                                 |
| --------------- | ----------------------------------------------------------------------- |
| Action ID       | Stable identifier used in workflow definitions                          |
| Category        | High-level family for discovery                                         |
| Tags            | Search and filtering details                                            |
| Connector       | Optional provider credential requirement                                |
| Input schema    | Required and optional fields accepted by the action                     |
| Output schema   | Result shape available to downstream expressions                        |
| Action behavior | Provider call, chain operation, or local utility work performed by B3OS |

## Provider and Connector Patterns

| Pattern                             | Example                                                                    |
| ----------------------------------- | -------------------------------------------------------------------------- |
| No connector                        | Public market or chain data lookup                                         |
| Wallet connector                    | EVM or Solana wallet-backed action                                         |
| Native connector                    | Slack, Shopify, Coinbase Business                                          |
| Pipedream connector                 | SaaS app coverage through Pipedream account integrations                   |
| Provider key configured by platform | Platform-level services such as chain data, search, or analytics providers |

## Where to Go Next

**[Action reference](/actions/reference)**

Schema-level reference for catalog actions, built-ins, logic actions, and triggers.
  **[Built-in actions](/actions/built-in)**

Control flow, data transforms, webhooks, managed data queries, delays, and child workflows.
  **[EVM onchain](/actions/evm-onchain)**

Wallet, contract, token, swap, and transaction workflows.

## Action Selection Checklist

1. Search by category, tag, provider, or action title.
2. Confirm required connector and wallet context.
3. Read the input schema before wiring expressions.
4. Check output schema before downstream references.
5. Add branch conditions before expensive or irreversible operations.
6. Test the node with representative input.