Overview

The Automation feature in Fireblocks allows you to create automation rules that automatically initiate certain actions based on the triggers and conditions you define. After these automation rules are created, they are saved on the Automation page and can be activated or deactivated as needed.

Creating, editing, deleting, activating, or deactivating automation rules can be done by the workspace Owner, Admins, Signers, and Editors, and all actions require Admin Quorum approval.

Automation rules are made up of three items:

• Triggers: The event that triggers the rule.
• Conditions: The criteria that must be met for an action to be initiated.
• Actions: The type of action that should be initiated.

Prerequisites

1. Create a dedicated automation user.
   • Until the automation user is set up, you can create automation rules but not activate them.
   • Currently, each workspace can only have one automation user.
2. Configure Transaction Authorization Policy (TAP) rules to allow the automation user to initiate transactions.
3. Set up an API Co-Signer to auto-sign transactions initiated by the automation user, enabling fully hands-off automation.
   • If you don’t set up a Co-Signer, you must manually sign all transactions resulting from your automation rules. If your rules are defined with short time periods, these transactions can back up. For this reason, we recommend using longer time periods for triggering automation rules if you choose to manually sign transactions.

Triggers

Automation rules are triggered based on one of two options:

• Time: The automation rule is triggered based on a predefined time. You can choose a time interval:
  • Minute and Hour: These time intervals allow you to define how frequently, in minutes or hours, the automation rule should be triggered. These time intervals are based on UTC. Automation rules with these time intervals are triggered at the next rounded interval. For example, a rule created to be triggered every 24 hours will trigger at 00:00 UTC regardless of when it was created.
  • Daily: This time interval allows you to define a specific time the rule should be triggered. This time interval is based on your local time zone.
  • Weekly: This time interval allows you to define the specific days and time the rule should be triggered. This time interval is based on your local time zone.
  • Monthly: This time interval allows you to define which day of each month and time the rule should be triggered. This time interval is based on your local time zone.
  • Range: This setting allows you to set an interval during a specific time of the day. For example, every 10 minutes between 08:00 and 17:00.
• Transaction: The automation rule is triggered based on a deposit, withdrawal, or any type of transaction involving one of your vault accounts. You can choose which vault account must send or receive the transaction to trigger the rule. You can also choose the type of asset that must be included in the transaction.

Example 1

• This automation rule is triggered every 2 hours, starting at 12:00 UTC.

Example 2

• This automation rule is triggered at 11:00 am (GMT-6) every Monday, Wednesday, and Friday.

Example 3

• This automation rule is triggered any time BTC is deposited to your Payment Account vault account.

Conditions

Automation rules are based on one of three options:

• Balance: The automation rule can be based on a specific amount or percentage of funds in the selected account. You can also choose which asset’s balance should trigger the automation rule and how it compares to the balance you define for the rule. If the automation rule’s condition is based on a percentage of funds, you must also select the accounts whose balances should be added together and compared to the original account’s balance.
• Transaction amount: The automation rule can initiate an action based on the amount of the transaction that triggered the rule. You can choose whether the asset must be equal, greater than, less than, greater than or equal to, or less than or equal to a defined amount for the action to be initiated. The value can be specified in either asset amount or USD.
• Unconditional: The automation rule can initiate an action without meeting any conditions. In this instance, the rule will automatically be triggered based on the time interval you chose for the Trigger.

Example 1

• This automation rule can initiate the action if the specific amount of BTC in your Treasury Wallets vault account is less than 1.

Example 2

• This automation rule can initiate the action if the amount of BTC in your Treasury Wallets vault account is less than 25% of the BTC in your Treasury Wallets and Payment Account vault accounts combined.

Example 3

• This automation rule can initiate the action if the amount of the transaction that triggered the rule is greater than or equal to 1 BTC.

Actions

Automation rules that are triggered, and their conditions met, will initiate the action you have configured. This action can be signed automatically by an API Co-Signer or manually using your mobile device.

There are four actions to choose from:

• Transfer: A defined amount of an asset is moved from one account to another. You can enter a specific amount, or the full amount of the asset. Select partial amount to leave either a percentage or specific balance in the source account.
• Top up: Additional funds for a specific asset are sent to the selected account to meet a defined balance for that account. You can choose which vault account should send the funds and which vault account or whitelisted address should be topped up.
• Rebalance: Funds are distributed between two accounts to meet a defined percentage. You can choose which asset should be rebalanced and the percentage each account should hold of that asset.
  • If you select a whitelisted address as one of the accounts, funds can only be transferred to the whitelisted address during the rebalance. Since your workspace does not have access to the signing keys for the whitelisted address, automation rules cannot move funds out of the whitelisted address.
  • If the whitelisted address is overweight according to the desired percentages for the rebalance and requires funds to be moved from the external account, the automation rule will fail.
• Payment flow: One of your payment flows is initiated. You can choose which payment flow to initiate and whether to use a specific amount, a percentage, the full amount, or an inherited amount of the asset. Inherited amount is only available if the asset defined in the Condition is the same asset defined in the first step in the payment flow.
  • This action is only available if you've purchased the Payments feature.
  • Payment flows must be created before you can include them in an automation rule. Learn more about creating payment flows.

Example 1

• This automation rule initiates a transaction of 10 ETH from your Treasury Wallets vault account to your Payment Account vault account.

Example 2

• This automation rule initiates a transaction of USDT from your Payment Account vault account to your Coinbase exchange account so that its balance is 10,000 USDT. If your balance on Coinbase is 7,000 USDT when the automation rule is triggered, a transaction of 3,000 USDT to your Coinbase account is initiated.

Example 3

• This automation rule initiates a transaction of ETH between your Payment Account vault account and your Master vault account so that each holds 50% of the ETH balance combined between those two accounts.

Example 4

• This automation rule initiates your SOL Transfer payment flow, which converts USD from your Bitso account to SOL and transfers the funds to the vault account defined in the flow. The payment flow will convert 500 USD from your Bitso account.

Example 5

• This automation rule initiates your USDC bridge payment flow using the inherited amount of USDC defined in the Transaction amount Condition.