> ## Documentation Index
> Fetch the complete documentation index at: https://docs.b3os.org/llms.txt
> Use this file to discover all available pages before exploring further.

# 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.

![Polymarket Deposit logo](https://cdn.b3.fun/b3os-icons/polymarket-icon.png)
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.

**Review wallet and value movement**

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 |
| --- | --- | --- | --- |
| `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. |
| `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. |
| `recipientAddress` | `string` | Yes | Deposit wallet address on Polygon that will receive pUSD. |

## 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

**Workflow node**

```json
{
  "type": "polymarket-deposit",
  "payload": {
    "recipientAddress": "0x0000000000000000000000000000000000000000"
  },
  "children": [],
  "connector": {
    "type": "wallet",
    "id": "conn_wallet"
  }
}
```
  **Test with API**

```bash
curl -X POST "https://api.b3os.org/v1/actions/polymarket-deposit/test" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "inputs": {
    "recipientAddress": "0x0000000000000000000000000000000000000000"
  }
}'
```

**Use expressions for dynamic values**

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.