Connect onOffice: API user, rights, token

Manage the connection under Settings → Integrations → onOffice.

1. Create an API user in onOffice#

1. 1

   Open user management

   In onOffice: Extras → Settings → Users.

2. 2

   Create the API user

   Create a new user and mark it as an API user (e.g. username reosa-api).

2. Generate token and secret#

Generate a token and a secret for the API user.

3. Grant the rights#

For every sync to work, the API user needs at least:

• Read addresses (all) and write (all).
• Read objects (all) and write (all).
• Disable the checkbox "can only read objects published on the website".
• Read and write agent log / activities (all).
• Enable "read user data via API" (for user selection lists).

4. Connect in the platform#

1. 1

   Open the integration

   Go to Settings → Integrations → onOffice.

2. 2

   Enter the credentials

   Leave the API URL as is (default: https://api.onoffice.de/api/stable/api.php). Enter token and secret.

3. 3

   Connect and test

   Click "Connect & test". On success the page shows "Connected".

5. Control the data flow#

After connecting, two switches let you decide what flows:

Fetch addresses from onOffice

The platform reads contacts and objects from onOffice. Nothing is changed in onOffice.

Write changes back to onOffice

The platform writes updates directly into your onOffice. Only enable this if the platform may write into your CRM.

Both switches ask for confirmation before any change, so nothing flips by accident.

6. Map team members#

Below the connection you find the list of your members, each with a field for the onOffice user. The platform suggests a mapping by email address; you can change or clear it at any time.

The mapping has three effects:

Tasks

A member only sees the tasks that run on their onOffice user.

Assignment

When DB-Leads assigns a contact, the platform writes this username into the configured onOffice field.

Agents log

Notes, call outcomes, the reasoning behind a readiness rating and entries made through the assistant appear in the agents log under this user, not under the API user. Entries a scan creates on its own stay with the API user.

Next#