Wallet automations

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 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 for available trigger and action types.

​

How automations fit together

Each trigger match creates an automation execution, 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, migrating assets between wallets, and other balance-management workflows. These are examples of future capabilities and aren’t supported today.

​

Next steps