> 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/testo-proheat/set-up-testo-proheat.md).

# Set up Testo ProHeat

Connect OutSmart to your Testo account with your security key.

Connect **OutSmart** to **Testo ProHeat** before you configure imports or exports.

You need the **Testo security key** from your Testo account.

### Before you start

Check these points first:

* the **Testo ProHeat** integration is active in the **License Manager**
* you have access to **Settings → General → Software integrations**
* you have the correct **Testo security key**

{% stepper %}
{% step %}

### Open Software integrations

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

Open **Testo ProHeat**.

Open **Settings**.
{% endstep %}

{% step %}

### Open the connection screen

If the integration is not connected yet, the login screen appears.

It asks for your **Testo security key**.
{% endstep %}

{% step %}

### Enter the security key

Paste the security key from your Testo account.

Then click **Connect**.
{% endstep %}

{% step %}

### Open the settings page

After a successful connection, OutSmart opens the Testo settings.

You can then review the import and export options.
{% endstep %}

{% step %}

### Choose the modules you use

Select **ProHeat**, **ProCool**, or both.

Only the selected modules are used in the sync.
{% endstep %}

{% step %}

### Configure imports and exports

Choose how customers and appliances should import.

Then choose how completed work orders should export.
{% endstep %}

{% step %}

### Save the setup

Click **Save**.

Your connection and settings are then stored.
{% endstep %}
{% endstepper %}

### What happens on the first connection

OutSmart creates Testo-specific custom fields automatically.

These fields are used to link records between both systems.

#### Object fields

OutSmart creates these fields on objects:

* **Object type**
* **Testo Pro+ ID**
* **Serial number**
* **Nominal power**
* **Brand**
* **Type**
* **Production year**

#### Work order fields

OutSmart creates this field on work orders:

* **Certification type** with **New** and **Periodic**

### Frequently asked questions

<details>

<summary>Where do I find the security key?</summary>

Use the **Help** button on the Testo settings page.

You can also use the documentation link on the login screen.

</details>

<details>

<summary>What happens if I disconnect the integration?</summary>

The synchronisation stops.

Existing data in OutSmart stays in place.

No new data syncs until you reconnect.

</details>

<details>

<summary>How do I know the connection works?</summary>

After you connect, the settings page opens normally.

The log panel on the right also starts showing sync activity.

</details>

<details>

<summary>Why does OutSmart create custom fields automatically?</summary>

These fields store the Testo identifiers and appliance data.

They keep customers, objects, and work orders linked correctly.

</details>

### Related topics

* [**Testo ProHeat**](/integrations/integrations/testo-proheat.md)
* [**What is Testo ProHeat?**](/integrations/integrations/testo-proheat/what-is-testo-proheat.md)
* [**Set up a software integration**](/integrations/integrations/set-up-a-software-integration.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/testo-proheat/set-up-testo-proheat.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.