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

# Create Address

Create a new Coinbase-custodied deposit address for a Coinbase Business account. The address can receive cryptocurrency from external wallets or on-chain transactions. Ideal for: receiving payments, treasury inflows, creating dedicated deposit addresses per customer or purpose.

![Create Address logo](https://ai-icon.b3.fun/logo/coinbase-business)
Catalog action Integrations coinbase-business

Create a new Coinbase-custodied deposit address for a Coinbase Business account. The address can receive cryptocurrency from external wallets or on-chain transactions. Ideal for: receiving payments, treasury inflows, creating dedicated deposit addresses per customer or purpose.


## At a Glance

| Field | Value |
| --- | --- |
| Action ID | `coinbase-business-create-address` |
| Category | Integrations |
| Connector | `coinbase-business` |
| Requires gas | No |
| Funds movement | None declared |
| Tags | `coinbase`, `address`, `deposit`, `receive`, `crypto`, `finance`, `write` |

## Payload Schema

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `accountId` | `string` | Yes | Account UUID — MUST be a UUID \(e.g., 'a9fee464-782f-5ace-b2d3-...'\). Do NOT pass a currency code like 'USDC'. Get the UUID by calling coinbase-business-get-account first, then use &#123;&#123;get_account.result.id&#125;&#125;. |
| `name` | `string` | No | Label for the address \(e.g., 'Treasury Deposit Address'\) |
| `network` | `string` | No | Network for the address \(e.g., 'base', 'ethereum'\) |
| `apiKeyName` | `string` | No | CDP API Key Name \(overrides connector\) |
| `apiKeySecret` | `string` | No | CDP API Key Secret \(overrides connector\) |

## Result Schema

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `id` | `string` | Yes | Address resource ID |
| `address` | `string` | Yes | On-chain address |
| `name` | `string` | No | Address label |
| `network` | `string` | Yes | Network name |
| `callbackUrl` | `string` | No | Callback URL for notifications |
| `createdAt` | `string` | Yes | Creation timestamp |
| `updatedAt` | `string` | Yes | Last update timestamp |

## Examples

**Workflow node**

```json
{
  "type": "coinbase-business-create-address",
  "payload": {
    "accountId": "a9fee464-782f-5ace-b2d3-123456789012"
  },
  "children": [],
  "connector": {
    "type": "coinbase-business",
    "id": "conn_coinbase_business"
  }
}
```
  **Test with API**

```bash
curl -X POST "https://api.b3os.org/v1/actions/coinbase-business-create-address/test" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "inputs": {
    "accountId": "a9fee464-782f-5ace-b2d3-123456789012"
  }
}'
```

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