Automations: Creating and Assigning Classification Rules

Note: You will need to have classifications set up in your Chart of Accounts prior to setting up classification automations. See Creating and Assigning Classifications

to learn how.

From the side panel, click on More Options, then select Automations.
Click on the + Classification Automation button.
Select Entity or Connection depending on which level you wish to apply this automation.
Click Next.
Complete the following fields.
1. Automation Name: Enter a name for the automation.
2. Automation Description: Optionally, enter a description.
3. Wallets or Accounts: Select whether the automation will apply to a wallet or an account.
4. Automation Sources: Click on Select, then select the wallets or accounts applicable and click Choose to confirm.
Click Next.
Criteria 1: Configure the condition that triggers this automation.
1. For instance, in this example, the trigger is: "When the Transaction Type is 'Receive' AND when the Contract Address is the one defined in the field".
2. You may customize the logical operators to match your preferences (Is, is not, or is empty).
3. You may add more than one condition if required by clicking + Add Condition.
Criteria 2: Configure the action that occurs when the trigger conditions are met.
1. Classification: applies a pre-defined classification to all transactions that meet the conditions (in Criteria 1).
2. Label: applies a pre-defined label to all transactions that meet the conditions (in Criteria 1).
3. For instance, in this example, the action is: to apply the classification "Deferred Revenue" to the matching transactions.
Click Next.
Review the trigger and the action and click Confirm to activate the classification rule. Your automation will be run when the conditions are met.

Automation Criteria #1: Detailed Descriptions

Criteria	Description
Destination address	Triggers the automation if the transaction’s recipient address matches a specific wallet address. Useful for tracking inbound payments to key wallets.
Origin address	Triggers when a transaction originates from a specific wallet or address you control. Ideal for monitoring outflows from designated sources.
Transaction tag	Filters transactions based on custom tags you or the system have applied. Great for grouping and acting on categorized transactions.
Transaction type	Targets transactions by their classification, such as trade, fee, airdrop, transfer, staking, etc. Helps in applying logic based on the nature of the activity.
Contract address	Applies automation if a smart contract address is involved in the transaction. Useful for DeFi-related workflows.
Internal transfer	Matches transactions that are internal transfers between wallets owned by your entity. Useful for excluding non-external activity.
Blockchain Function	Filters transactions that call specific smart contract functions, such as `stake`, `mint`, or `swap`. Useful for identifying on-chain operations.
Destination address group	Matches any destination address that belongs to a predefined address group you’ve set up—ideal for applying rules to clusters of recipient wallets.
Origin address group	Same as above but for source addresses. Helps apply consistent rules across a group of sending wallets.
Contract address group	Filters transactions involving any contract from a saved list of contract addresses. Streamlines logic for commonly used DeFi protocols or platforms.
Date Range	Applies automation to transactions within a specific date range. Useful for time-bound reconciliations or reporting periods.
Asset	Filters based on the cryptocurrency/token used in the transaction (e.g., ETH, USDT). Allows precise control over which assets trigger actions.
Label	Triggers based on labels assigned to transactions (manually or automatically). Ideal for building rules based on business context.
Market Pair	Targets specific trading pairs, like BTC/USDT or ETH/DAI. Useful in trading or portfolio rebalancing automations.
Transaction Amount (Crypto Amount)	Triggers based on the crypto value in a transaction. Allows rules to apply only above or below certain thresholds (e.g., transactions over 10 ETH).
Memo	Filters transactions by the memo or note field, which can be used for internal references or external transaction identifiers.
Program ID	Applies to transactions involving a specific Solana program ID. Useful for Solana-based automations and smart contract tracking.
NFT Symbol	Triggers when the transaction involves a specific NFT or collection, identified by its symbol. Enables automation for NFT-specific use cases.
Executor Contract	Filters transactions based on the smart contract that executed the action. Often used when the source of execution matters more than the token or address.
Method ID	Triggers based on the smart contract method (function) signature (e.g., 0xa9059cbb for `transfer`). Useful for highly technical filtering.
Executor contract group	Matches any executor contract from a group of known or saved contracts. Helpful in applying rules across similar contract types.
Method ID group	Like Method ID, but checks against a group of functions, allowing broader filtering across related smart contract actions.
Commitment ID	Targets transactions tied to a specific commitment or funding reference (often for internal workflows or compliance purposes).
Asset Support	Filters transactions by the support status of the asset—e.g., supported, unsupported, or limited in the platform. Useful for flagging risky or unsupported activity.
Connection Group(s)	Filters by wallets or exchange accounts grouped by team, business unit, or integration. Useful for assigning rules to specific account clusters.