Aerodrome Claim Fees
Claim accumulated trading fee rewards for a veNFT on Aerodrome Finance (Base). Use aerodrome-get-claimable-rewards first to discover claimable fees. Groups fees by fee contract and calls Voter.claimFees in a single transaction. Ideal for: automated fee harvesting, veNFT reward collection, DeFi yield automation.
Catalog action EVM Onchain wallet Gas receive
Claim accumulated trading fee rewards for a veNFT on Aerodrome Finance (Base). Use aerodrome-get-claimable-rewards first to discover claimable fees. Groups fees by fee contract and calls Voter.claimFees in a single transaction. Ideal for: automated fee harvesting, veNFT reward collection, DeFi yield automation.
This action can require a wallet connector, gas, token movement, or an external side effect. Test with simulation or a controlled amount before using it in a live workflow.
At a Glance
| Field | Value |
|---|---|
| Action ID | aerodrome-claim-fees |
| Category | EVM Onchain |
| Connector | wallet |
| Requires gas | Yes |
| Funds movement | receive |
| Tags | defi, fees, claim, base, onchain, write |
Payload Schema
| Field | Type | Required | Description |
|---|---|---|---|
chainId | number | Yes | Chain ID. Supported: Base (8453) |
tokenId | string | Yes | The veNFT token ID to claim fees for |
claimableFees | array | Yes | Array of claimable fee items from aerodrome-get-claimable-rewards. Each item must include feeAddress and tokenAddress. |
Result Schema
| Field | Type | Required | Description |
|---|---|---|---|
skipped | boolean | No | True if no claimable fees were found and the claim was skipped |
reason | string | No | Reason the claim was skipped (only present when skipped is true) |
txHash | string | null | No | Transaction hash of the claim (null when skipped) |
tokenId | string | Yes | The veNFT token ID claimed for |
claimed | array | No | Items that were claimed (empty when skipped) |
Examples
json{ "type": "aerodrome-claim-fees", "payload": { "chainId": 8453, "tokenId": "1", "claimableFees": [] }, "children": [], "connector": { "type": "wallet", "id": "conn_wallet" }}
bashcurl -X POST "https://api.b3os.org/v1/actions/aerodrome-claim-fees/test" \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "inputs": { "chainId": 8453, "tokenId": "1", "claimableFees": [] }}'
Payload fields can use workflow expressions such as {{$trigger.body.amount}}, {{$nodes.fetch.result.price}}, and {{$props.asset}} when the value should come from a trigger, prior node, or reusable workflow prop.