Wallet automations

Wallet automations define how a wallet responds to an event. An automation is 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. Wallet automations currently support deposit triggers with swap actions through crypto deposit addresses.

​

Why use automations

Without an automation, an app’s backend must monitor chains, deduplicate events, and submit wallet actions. Wallet automations move that operational loop to Privy while the 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 processing an incoming deposit. 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.

​

Authorization and policies

Authorization applies at three levels: An attachment authorizes future actions that match its configured trigger, action, wallet, and parameters. Executions do not require a new wallet-owner signature. An attachment does not grant an automation general-purpose signing authority. Imported wallets and wallets previously exported from Privy cannot receive automation attachments.

​

Matching behavior

A wallet can have several attached automations, but Privy selects only the oldest enabled attachment that matches a detected deposit. Overlapping automations do not all run. Use non-overlapping asset filters unless attachment order intentionally defines priority.

​

Next steps