onOffice CRM Integration
Create every lead as an address in onOffice - with the valuation PDF, duplicate merging and an optional property record.
Last updated: 2026-09-02
The onOffice integration creates every new lead as an address in your onOffice account — with contact data, property data and, if you want it, the finished valuation as a PDF.
Setup happens entirely in fluss.ai. You no longer need our team to switch it on for you.
Setup
- Create an automation of type CRM integration
- Choose onOffice as the provider
- Enter your API token and API secret, then click Test connection
- Check the field mapping — the defaults match the table below
- Save the automation and attach it to your flow
The connection test tells you immediately whether your credentials and address access work. It reads a single record and writes nothing to your onOffice account. You can re-run it any time without retyping the credentials.
The token and secret are stored encrypted and not shown again. When editing, leave the fields empty to keep them, or enter a new value to replace them.
Creating the API credentials
- Sign in to onOffice
- Go to Tools → Settings → API
- Create an API user
- Note down the token and the secret
onOffice shows the secret once. Copy it while you are creating the API user — otherwise you have to create a new one.
The API user needs at least permission to create addresses. Attaching the valuation and creating properties need the matching permissions on top.
Transferred fields
This mapping is preconfigured and fully editable. On the left is the field name in onOffice, on the right what goes into it — type {{ to insert a variable.
| onOffice field | Value |
|---|---|
Anrede | {{Anrede}} |
Vorname | {{Vorname}} |
Name | {{Nachname}} |
email | {{email}} |
phone | {{phone}} |
Plz | {{PLZ}} |
Strasse | {{Straße}} |
Ort | {{Stadt}} |
Use Add field to include more onOffice fields, and Reset to defaults to restore the table.
Fields whose value is empty for a given lead are left out instead of being written as "-". onOffice ends up with an empty field, not a placeholder.
See the variable reference for everything you can insert.
Options
Contact origin (HerkunftKontakt)
Sets the HerkunftKontakt field on the address. The value has to match an entry configured in your onOffice account — Load options pulls the list straight from it. With nothing selected, no origin is sent.
Merge duplicates
On by default. When onOffice already knows the contact, the existing address is extended instead of a second one being created.
The existing contact is never overwritten. Whatever a colleague typed in by hand stays put — even when the same owner fills in the form a second time.
Attach the valuation PDF
Off by default. Uploads the generated valuation as a document on the address, named after the pattern Marktwertschaetzung-Mustermann-50667.pdf. If the lead has no valuation yet the step is skipped — the address is still created.
If you want the valuation to come along, order the CRM integration after the valuation step in your automations. Otherwise it runs before a PDF exists.
Also create the property
Creates the valued property as an object in onOffice as well, and links the lead to it as owner. That puts the valuation into your acquisition pipeline, not just your contacts.
| onOffice field | Value |
|---|---|
objekttitel | {{Straße}}, {{PLZ}} {{Stadt}} |
nutzungsart | wohnen |
land | DEU |
strasse | {{StraßeOhneNummer}} |
hausnummer | {{Hausnummer}} |
plz | {{PLZ}} |
ort | {{Stadt}} |
wohnflaeche | {{WohnflächeZahl}} |
grundstuecksflaeche | {{GrundstücksflächeZahl}} |
anzahl_zimmer | {{Zimmeranzahl}} |
baujahr | {{Baujahr}} |
Created objects are never published. They stay out of your website and your portals until you publish them yourself.
The option is off by default — your inventory is yours.
Requirements
- An active onOffice account
- fluss.ai Pro or higher (CRM integrations are available from the Pro plan)
- An onOffice API token and secret
Once active, all new leads are transferred. Existing leads are not synchronized retroactively.
Troubleshooting
The connection test fails. The message comes straight from onOffice. Usually the secret was not copied in full, or the API user has no permission for addresses.
The address is created but a field stays empty. Check the spelling of the onOffice field name in the mapping — onOffice is case-sensitive (Plz, not PLZ).
The origin is not applied. The value has to match an entry configured in your account exactly. Load the options and pick one from the list.
The PDF is missing. The valuation did not exist yet when the transfer ran. Move the CRM integration after the valuation step.
If you connect onOffice through your own automation instead of this
integration: onOffice answers with HTTP 200 even on failure and puts the
error in the body. Check the body, not just the status — otherwise failed
transfers look like successes.
Questions about setup? Contact our support team at support@fluss.ai.