> For the complete documentation index, see [llms.txt](https://docs.shippercrm.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shippercrm.com/settings/organization/integrations.md).

# Integrations

## HubSpot

As of July 31st, 2024 ShipperCRM users can synchronize any contacts & companies they have saved from the MagicMap into their HubSpot account. Currently, this integration is 1-way: from ShipperCRM to HubSpot. In the future we will allow users to move over their contacts from HubSpot to ShipperCRM.

#### Configure the HubSpot Integration

<figure><img src="/files/DSBWh4nML2jxs6oXES2U" alt=""><figcaption><p>Setup the integration by going to the Settings > Integration page in ShipperCRM</p></figcaption></figure>

### Follow the HubSpot authentication instructions

After clicking 'Set up', we will direct you to login into your HubSpot account. If you are already logged in, then this should be immediate.&#x20;

### Confirm required data access

HubSpot will ask you to confirm the data that will be shared with ShipperCRM required to safely copy over your ShipperCRM contacts into your HubSpot account.&#x20;

{% hint style="info" %}
ShipperCRM only uses your existing HubSpot data to resolve potential duplicate contact conflicts. We first need to check if the contact already exists in HubSpot, and if it does not, then we will create a new contact automatically.
{% endhint %}

### How we handle contacts that already exist in HubSpot

If the contact already exists in HubSpot, we currently synchronize the contact in HubSpot to have the phone numbers and emails that exist for that contact in ShipperCRM.

Example:

* Douglas Adams at Walmart exists in HubSpot and has 2 phone numbers and 1 email
* Douglas Adams at Walmart also exists in ShipperCRM with 2 phone numbers and 1 email

The phone numbers and emails for Douglas Adams in ShipperCRM will be copied into the Douglas Adams in HubSpot.


---

# 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.shippercrm.com/settings/organization/integrations.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.