Skip to main content
Automation definitions are app-scoped and reusable. Attachments activate those definitions for individual wallets.

List automations

List all definitions with GET /v1/wallet_automations. Pass wallet_id to return only automations attached to one wallet. The Node SDK and Python examples initialize reusable clients here. The remaining examples on this page reuse those clients.

Update or pause an automation

PATCH /v1/wallet_automations/{automation_id} can update name, config, or enabled.
Disabling an automation pauses it for every attached wallet. Attachments remain in place and resume when the automation is enabled again.
Updating config changes the trigger and action for every attached wallet. Create a separate automation when only some wallets should adopt the new behavior.

Matching precedence

A wallet can have multiple attached automations. Privy evaluates enabled attachments from oldest to newest and runs only the first matching automation. Use non-overlapping asset filters when every route must be unambiguous. If filters intentionally overlap, attach the highest-priority automation first. Detaching and later reattaching an automation creates a new attachment. The new attachment is evaluated after older attachments.

Detach from a wallet

Detaching stops selected automations for one wallet without changing their other attachments.
A successful private-key or seed-phrase export also removes all automation attachments from that wallet. This prevents an exported wallet from remaining enrolled in previous automation consent.

Delete an automation

Deleting an automation permanently removes its definition and all attachments. Existing execution and wallet action records remain available for auditing. Use disable when the automation might resume. Use detach to stop it for selected wallets. Delete only when the definition is no longer needed.

Advanced: automation ownership

Set owner_id during creation to assign a key quorum as the automation owner. The owner protects the shared definition. The wallet owner separately controls whether that definition is attached to their wallet.

Limits

  • An attach or detach request accepts up to 20 automation IDs.
  • An include or exclude filter accepts up to 20 asset specifications in an API request.
  • A wallet can have up to 100 automation attachments.
  • List endpoints accept limit values from 1 through 100 and default to 25.
See the wallet automation API reference for request and response schemas.