Sign and Claim Allocation
Sign and submit a Magna allocation claim transaction on-chain (EVM only). Accepts unsigned transaction data from the Request Claim Allocation action, signs with Turnkey wallet, and broadcasts. Ideal for: automated token claiming, end-to-end vesting claims, scheduled claim workflows.
Catalog action EVM Onchain wallet Gas receive
Sign and submit a Magna allocation claim transaction on-chain (EVM only). Accepts unsigned transaction data from the Request Claim Allocation action, signs with Turnkey wallet, and broadcasts. Ideal for: automated token claiming, end-to-end vesting claims, scheduled claim workflows.
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 | magna-sign-and-claim |
| Category | EVM Onchain |
| Connector | wallet |
| Requires gas | Yes |
| Funds movement | receive |
| Tags | magna, claim, vesting, token, transaction, write, on-chain |
Payload Schema
| Field | Type | Required | Description |
|---|---|---|---|
to | string | Yes | Target contract address from the claim allocation response. |
data | string | Yes | Encoded transaction calldata from the claim allocation response. |
chainId | number | Yes | The EVM chain ID where the claim transaction will be submitted. |
transactionId | string | No | Magna's internal transaction identifier from the claim allocation response. |
platformFee | string | null | No | Platform fee from the claim-allocation response. When present, this value (in ETH/native token) is sent as the transaction value (msg.value). |
waitForConfirmation | boolean | No | Whether to wait for transaction confirmation (default: true). |
Result Schema
| Field | Type | Required | Description |
|---|---|---|---|
transactionHash | string | Yes | The transaction hash of the submitted claim transaction. |
blockNumber | number | No | Block number where the transaction was confirmed. |
from | string | No | The wallet address that signed the transaction. |
transactionId | string | No | Magna's internal transaction identifier. |
chainId | number | Yes | The chain ID where the transaction was submitted. |
Examples
json{ "type": "magna-sign-and-claim", "payload": { "to": "example-to", "data": "example-data", "chainId": 8453 }, "children": [], "connector": { "type": "wallet", "id": "conn_wallet" }}
bashcurl -X POST "https://api.b3os.org/v1/actions/magna-sign-and-claim/test" \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "inputs": { "to": "example-to", "data": "example-data", "chainId": 8453 }}'
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.