Polymarket Deposit
Deposit funds into a Polymarket deposit wallet via cross-chain bridge (Relay Protocol). Accepts tokens from any supported chain and bridges to pUSD on Polygon. Ideal for: funding a Polymarket trading wallet to place bets.
Catalog action EVM Onchain wallet
Deposit funds into a Polymarket deposit wallet via cross-chain bridge (Relay Protocol). Accepts tokens from any supported chain and bridges to pUSD on Polygon. Ideal for: funding a Polymarket trading wallet to place bets.
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 | polymarket-deposit |
| Category | EVM Onchain |
| Connector | wallet |
| Requires gas | No |
| Funds movement | None declared |
| Tags | polymarket, wallet, write |
Payload Schema
| Field | Type | Required | Description |
|---|---|---|---|
amount | string | Yes | Amount to deposit (human-readable, e.g., '100' for 100 USDC). |
chainId | number | No | Source chain to pull tokens from. Defaults to Polygon (137). Supported: 1 (Ethereum), 10 (Optimism), 137 (Polygon), 8453 (Base), 42161 (Arbitrum), 43114 (Avalanche). |
tokenAddress | string | No | Token address on the source chain to swap from. Defaults to USDC. When a non-USDC token is provided, Relay Protocol swaps it to pUSD and bridges to Polygon. |
recipientAddress | string | Yes | Deposit wallet address on Polygon that will receive pUSD. |
amountRaw | string | No | Raw amount in the source token's smallest units (e.g., wei). Required when tokenAddress is a non-USDC token. Takes precedence over the amount field when provided. |
Result Schema
| Field | Type | Required | Description |
|---|---|---|---|
status | string | Yes | Deposit outcome |
transactionHash | string | No | Transaction hash on the source chain |
depositedAmount | string | No | Amount deposited in smallest token units (e.g., '100000000' for 100 USDC) |
sourceChainId | number | No | Chain ID the funds were bridged from |
Examples
json{ "type": "polymarket-deposit", "payload": { "amount": "1000000", "recipientAddress": "0x0000000000000000000000000000000000000000" }, "children": [], "connector": { "type": "wallet", "id": "conn_wallet" }}
bashcurl -X POST "https://api.b3os.org/v1/actions/polymarket-deposit/test" \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "inputs": { "amount": "1000000", "recipientAddress": "0x0000000000000000000000000000000000000000" }}'
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.