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

# deal.created

> Outbound webhook when a new deal is created.

# `deal.created`

## What this event means

`deal.created` is emitted whenever a new deal is created in Klipy.

## Webhook `type`

`deal.created`

## Internal source mapping

| Internal event | Trigger path                                        |
| -------------- | --------------------------------------------------- |
| `deal.created` | Deal creation mutation persisted a new deal record. |

## Payload example

```json theme={null}
{
  "type": "deal.created",
  "object": "event",
  "data": {
    "deal_id": "dl_1a2b3c",
    "pipeline_id": "pl_b4c5d6",
    "pipeline": "Q4 Pipeline",
    "estimated_value": 18500,
    "currency": "USD",
    "deal_creation_date": "2026-04-20T09:21:11.122Z",
    "estimated_close_date": "2026-06-01T00:00:00.000Z",
    "is_private": false,
    "deal_name": "Acme Analytics - Expansion plan",
    "owner_name": "Alex Morgan",
    "company": {
      "name": "Acme Analytics",
      "domain": "acmeanalytics.com"
    },
    "point_of_contact": {
      "first_name": "Jordan",
      "last_name": "Patel",
      "email": "jordan.patel@acmeanalytics.com",
      "title": "Head of Growth"
    }
  }
}
```

## Delivery and idempotency handling

* Keep processing idempotent; duplicate deliveries are possible during retries.
* For dedupe and merge logic, use `data.deal_id`.
* Optional fields are populated depending on enrichment availability. Persist defensively when only partial fields are present.
* Only acknowledge after the deal has been saved in your downstream system.

## Related links

* [Webhook introduction](/docs/webhooks/introduction)
* [Webhook event types](/docs/webhooks/event-types)