> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/integrations/integrations/yuki/configure-yuki-imports.md).

# Configure Yuki imports

Use the import settings to decide which data OutSmart pulls from Yuki.

Yuki currently imports **relations** into OutSmart.

### Available import option

#### Relations

OutSmart imports Yuki relations as customers.

This includes both people and companies.

The import can include:

* name
* address
* city
* postal code
* country
* email address
* phone number

OutSmart only imports **active** relations.

Only relations created or updated on or after the **sync date** are included.

### How matching works

If the Yuki relation already matches an existing customer in OutSmart, OutSmart updates that customer.

If no match is found, OutSmart creates a new customer.

### Automatic and manual imports

The integration runs automatically in the background.

You can also trigger a manual import with the sync icon next to **Relations**.

{% stepper %}
{% step %}

### Open the Yuki settings

Go to **Settings → General → Software integrations**.

Open **Yuki**.
{% endstep %}

{% step %}

### Enable relation import

In **Import settings**, enable **Relations**.
{% endstep %}

{% step %}

### Check the sync date

Make sure the **Sync date** is correct.

Only changed relations from that date onward are imported.
{% endstep %}

{% step %}

### Save the settings

Click **Save**.

The automatic import is then active.
{% endstep %}

{% step %}

### Run a manual import if needed

Click the sync icon next to **Relations**.

OutSmart starts the import immediately.
{% endstep %}
{% endstepper %}

### Important to know

* Only **active** relations are imported.
* Both **companies** and **persons** are supported.
* The sync date limits which changed records are included.
* You can run the import manually at any time.

### Frequently asked questions

<details>

<summary>Are inactive relations imported?</summary>

No.

OutSmart only imports active Yuki relations.

</details>

<details>

<summary>Can I import only recent changes?</summary>

Yes.

Use the **Sync date** to define the starting point.

OutSmart only imports relations created or updated after that date.

</details>

<details>

<summary>What happens when a customer already exists in OutSmart?</summary>

OutSmart updates the existing customer when the Yuki relation matches it.

Otherwise OutSmart creates a new customer.

</details>

### Related topics

* [**Yuki**](/integrations/integrations/yuki.md)
* [**Set up Yuki**](/integrations/integrations/yuki/set-up-yuki.md)
* [**Configure Yuki exports**](/integrations/integrations/yuki/configure-yuki-exports.md)
* [**Troubleshoot Yuki**](/integrations/integrations/yuki/troubleshoot-yuki.md)


---

# 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://knowledge.out-smart.com/integrations/integrations/yuki/configure-yuki-imports.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.