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

# Coinbase Payment Received

Triggers when a Coinbase Business payment link receives a payment (success, failed, or expired).

Trigger Commerce

Triggers when a Coinbase Business payment link receives a payment (success, failed, or expired).

## At a Glance

| Field | Value |
| --- | --- |
| Trigger ID | `coinbase-payment-received` |
| Category | Commerce |
| Tags | `coinbase`, `payment`, `crypto`, `payment-link`, `webhook` |

## Trigger Configuration

This trigger does not require configuration fields.

## Trigger Result

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `triggeredAt` | `string` | Yes | - |
| `eventType` | `string` | No | Coinbase event type \(e.g. payment_link.payment.success, payment_link.payment.failed, payment_link.payment.expired\) |
| `paymentLink` | `object` | Yes | Full Coinbase payment link event object |

## Workflow Root Example

```json
{
  "nodes": {
    "root": {
      "type": "coinbase-payment-received",
      "payload": {},
      "children": [
        "log_event"
      ]
    },
    "log_event": {
      "type": "log",
      "payload": {
        "message": "Triggered at {{$trigger.triggeredAt}}"
      },
      "children": []
    }
  }
}
```

**Reference trigger output**

Downstream nodes can use `{{$trigger.triggeredAt}}` and any result fields listed above. Event triggers usually expose the raw source payload under a field such as `event`, `body`, `trade`, or `raw`.