> For the complete documentation index, see [llms.txt](https://docs-vnext.kiflo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-vnext.kiflo.com/integrations/hubspot/how-to-register-a-deal-that-already-exists-in-hubspot.md).

# How to register a deal that already exists in HubSpot?

You may want to register a deal in Kiflo on behalf of a partner and that deal is already created in your HubSpot account. If you register the deal as usual, Kiflo will create a new duplicate deal in HubSpot. And you don't want that.

To avoid this behavior, follow the instructions below. Kiflo will not create a new deal and will sync with the existing deal in HubSpot.

{% hint style="info" %}
**In this article**

[Prerequisites](#prerequisites)

[Register existing deal](#register-existing-deal)
{% endhint %}

## Prerequisites <a href="#prerequisites" id="prerequisites"></a>

To register a deal in Kiflo that already exists in HubSpot, make sure you fulfill the following conditions:

* [HubSpot integration is enabled](/integrations/hubspot/hubspot.md#enable-hubspot-integration)
* [The workflow "Create Deal in HubSpot when Deal is created/accepted in Kiflo" is enabled](/integrations/hubspot/hubspot.md#turn-on-settings):

![](https://3041514930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKkJn82Qo5a0Y4fOsoQzo%2Fuploads%2Fgit-blob-cda5771ec46c4d88372f2a5e2ca48df3bcbae001%2F689c6d56f6e00f17753751ad.png?alt=media)

* [The property "HubSpot Deal ID" is visible on your deal reg form](/account-settings/properties/customize-properties.md)

{% hint style="warning" %}
**Caution**

Kiflo may override the deal stage in HubSpot upon registration depending on your configuration. To avoid this behavior customize the ***sync rule*** on deal stages to be: "Prefer HubSpot".

[How to change the sync rule on deal deals?](/integrations/hubspot/how-to-map-deal-stages-with-hubspot.md#choose-the-sync-rule)
{% endhint %}

## Register existing deal <a href="#register-existing-deal" id="register-existing-deal"></a>

Go to the **Deals** page:

* Click the **Register deal** button
* Choose the partner who is assigned on that deal
* Fill in only those two fields on the deal reg form:
  * **Name**: Just for reference, it may be overriden later according ot your HubSpot settings
  * **HubSpot Deal ID**: The *record ID* of the existing deal in HubSpot

That's it! Now, wait a few minutes the time for Kiflo to pull the existing deal and map the other fields automatically.

{% hint style="info" %}
**What if I want to provide additional information to partners?**

The minimum requirement is to fill in the *deal name* and *HubSpot deal ID*. But you can provide additional information, for instance for fields that are not synced with HubSpot.

The idea behind providing only *deal name* and *HubSpot deal ID* is to avoid double entry as Kiflo will pull data from HubSpot anyway.
{% endhint %}

### Where to find the HubSpot record ID?

In HubSpot, on the deals's page:

* View all properties
* Search for "record id"
* Copy the value (it must look as follows):

![](https://3041514930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKkJn82Qo5a0Y4fOsoQzo%2Fuploads%2Fgit-blob-a564340d3f54ea328c5de36c36fc846191aef212%2F689c712683797137402c167e.png?alt=media)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs-vnext.kiflo.com/integrations/hubspot/how-to-register-a-deal-that-already-exists-in-hubspot.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
