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

# Wallet automations

> Define policy-controlled wallet actions that Privy runs in response to events.

Wallet automations let you define how a wallet should respond to an event. Think of an automation as a reusable intent: when a configured **trigger** occurs, Privy submits a configured **action**.

Attach the same automation to many wallets while controlling which wallets can run it. Wallet owner authorization and [wallet policies](/controls/policies/overview) continue to apply.

## Why use automations

Without an automation, your backend must monitor chains, identify and deduplicate relevant events, submit wallet actions, and recover from failures. Wallet automations move that operational loop to Privy while your app retains control over configuration, authorization, and policy.

This is useful for wallet behavior that should run reliably outside your app's lifecycle.

The following flow shows an automation converting an incoming deposit into a configured destination asset. See [configure triggers and actions](/controls/automations/configuration) for available trigger and action types.

```mermaid theme={"system"}
flowchart LR
    deposit[Deposit arrives] --> match[Match an enabled attachment]
    match --> execution[Create an automation execution]
    execution --> action[Submit a swap wallet action]
    action --> destination[Send output to the configured destination]
```

## How automations fit together

| Resource      | Scope  | Purpose                                                                          |
| ------------- | ------ | -------------------------------------------------------------------------------- |
| Automation    | App    | Defines the trigger, asset filter, and action.                                   |
| Attachment    | Wallet | Enables an automation for a wallet and records the address that receives output. |
| Execution     | Event  | Records one matched trigger and the wallet action created to fulfill it.         |
| Wallet action | Wallet | Exposes the action's onchain status, steps, and transaction identifiers.         |

Each trigger match creates an [automation execution](/controls/automations/lifecycle), which records why the automation ran and links to the wallet action that carries out the onchain operation.

## Where automations are going

The trigger-action model is designed to support more wallet workflows over time. Planned directions include automatically depositing eligible balances into [Earn vaults](/wallets/actions/earn/overview), migrating assets between wallets, and other balance-management workflows. These are examples of future capabilities and aren't supported today.

## Next steps

<CardGroup cols={2}>
  <Card title="Configure an automation" href="/controls/automations/configuration" icon="sliders">
    Choose a trigger, filter, action, and per-wallet parameters.
  </Card>

  <Card title="Create and attach an automation" href="/controls/automations/create-and-attach" icon="play">
    Configure a deposit trigger and enable it for a wallet.
  </Card>

  <Card title="Understand the lifecycle" href="/controls/automations/lifecycle" icon="clock">
    Monitor automation executions and their wallet actions.
  </Card>

  <Card title="Use webhooks" href="/controls/automations/webhooks" icon="webhook">
    Receive an event when an automation submits a wallet action.
  </Card>

  <Card title="Manage automations" href="/controls/automations/manage" icon="sliders">
    Update, pause, detach, and delete automations safely.
  </Card>
</CardGroup>