The onOffice API module is a paid add-on. Ask your onOffice account manager to enable it before you connect, and check what onOffice charges for API use.
Set up your account
- In onOffice enterprise, open Extras → Settings → User and create an API user for the assistant only.
-
Give the API user these rights:
- Addresses: read and write.
- Properties: read.
- Calendar: write.
- Agent’s log (Maklerbuch): write.
- Copy the API token (32 characters) and the API secret (64 characters). onOffice shows the secret once. If the connection says that token and secret look swapped, enter them the other way round.
- Open Agent Tools → Marketplace → onOffice, enter token and secret and choose the settings below if yours differ from the defaults. Choose Add. The connection is checked before it is saved. Then assign it to your assistant.
What the assistant can do
Enabled by default:- Find properties by street, town, buy or rent, property type, rooms, budget or the property number from an advert.
- Property details: price, rooms, areas, floor, year, condition, heating, costs, pets, description and availability.
- Free viewing times in the calendar of the responsible agent.
- Book viewings after the caller confirms.
- Create prospects with a search profile after the caller agrees.
- Recognise the caller by phone number.
- Call notes: write a note about a finished call into the agent’s log. It is meant for automations, see below.
Which properties the assistant sees
The setting Properties the assistant may talk about decides:- Published on your website (default): active properties that are published on your website.
- Marketing status open: active properties that are neither sold or rented nor reserved, published or not.
Viewings
The assistant books a viewing in the calendar of the property’s responsible agent. A property without a responsible agent uses the Default agent from the settings. Without both, the property cannot be booked and the assistant offers a callback from the team.- Times: from tomorrow, every day including weekends, inside the Viewing hours (default 08:00–18:00) in your time zone. Slots follow a 30-minute grid and last as long as Viewing length (default 30 minutes).
- Busy times: any calendar entry of that agent counts as busy. All-day entries block the whole day. Cancelled entries do not count.
- Booking: the assistant asks for first and last name, reads back property, day and time and waits for a clear yes. It checks once more that the time is free, then creates the appointment, linked to the property and the contact. It says “booked” only after onOffice confirmed.
- Contacts: a contact with the caller’s number is reused. Several contacts with one number are told apart by last name. Otherwise a new contact is created, with an e-mail address only if the caller gave one.
- Withheld numbers: callers who hide their number cannot book. The assistant offers a callback.
Besichtigung). Its note names who booked it, in your brand.
A timeout does not prove that a booking failed. Repeated requests are protected against double bookings. If the assistant reports an unknown outcome, check the agent’s calendar before booking again.
Prospects
When a caller is looking for a property, the assistant collects first and last name, buy or rent and whatever the caller names: town, type, rooms and budget. After a clear yes, it saves the caller as a contact and adds a search profile with these wishes.- A contact with the same number is reused instead of duplicated.
- No e-mail address is written unless the caller gave one. There is no placeholder address.
- The profile only contains criteria that your onOffice account offers as search criteria.
- If onOffice rejects the profile, the contact stays and the assistant says that the team will add the wishes.
Call notes in the Maklerbuch
Call notes are off for assistants. Use the automation template Log calls in onOffice (New → Start from template, category CRM): after each inbound call with a summary, onOffice is searched for contacts with the caller’s number, up to three, and a note is written into their agent’s log. The note starts with “Call with” and your brand, then the summary and the call length.- Switch on Call notes for the connection under Automations → Connections: it is off by default, and the template fails until you do. Use a connection created there, not one imported from the Agent Tool, so the assistant does not get call notes.
- The Action kind and Action type for call notes (default
TelefonatandEingang) must exist in onOffice. If they do not, the connection still saves, but call notes are refused with a hint. - Callers who are not in onOffice get no note.
- The call link is not written.
- Templates are not shown in reseller customer workspaces. Build the same automation with the action onOffice · Call notes; the phone number is not entered, it comes from the call.
Recognising callers
When the caller’s number matches exactly one active contact, the assistant greets by name. If several contacts share the number, it asks for the last name. If the number is withheld or unknown, it treats the caller as new. Properties are public data, so they need no check. The assistant never reads out e-mail addresses, phone numbers or addresses from your contacts.Settings
Change these under Automations → Connections, or remove the tool and connect again. Booking, prospects and call notes are switched under Edit of the tool.Test safely
Bookings, prospects and notes are real. Test with a test property, a calendar you can clean up and your own phone number, then delete the test appointment and the test contact in onOffice. Text simulations do not call onOffice.Channels
Property search and details work on every channel. Recognition, viewings and prospects use the phone number the conversation carries: phone, WhatsApp and SMS have one. Web chat and email do not, so the assistant offers a callback instead of booking.Automations
Every operation is an action under onOffice · …. Connect onOffice under Automations → Connections, or import its Agent Tool connection. An automation started by a call or a text conversation knows the number of the other party from that call itself, never from the trigger data or a step input, so Call notes takes no phone number. Runs started in another way (webhook, schedule) have no number: booking and prospects answer that it is not available, and call notes write nothing. A manual run has a number only when its run data names a call or conversation of your workspace. Triggers for new properties or contacts are not available yet.API, MCP, CLI & SDK
POST /api/v1/tools/integrations/onoffice · MCP connect_integration · CLI famulor connect-integration onoffice.
The tool starts with property search, viewings and prospects enabled. client.api.connectIntegration needs famulor-sdk 0.2.12 or later. Update the CLI with npm install --global famulor before you use connect-integration.
estate_rule (published or open), default_agent, viewing_type, viewing_minutes, viewing_hours, log_action_kind, log_action_type and timezone.
Troubleshooting
- “onOffice did not accept the API token, secret or rights.” Check both values, check that the API user is active and has the rights above, and create a new token and secret if you regenerated them in onOffice.
- “onOffice rejected the signature.” Token and secret are swapped or the secret was copied incompletely. The token has 32 characters, the secret 64.
- “The server clock is out of sync with onOffice.” This is temporary. Try again later.
- Searches find nothing although the properties exist. Check that the read rights cover all records, not “only own”, and that the property matches Properties the assistant may talk about.
- “Check the appointment type.” Set Appointment type for viewings exactly as the type of action for appointments is named in onOffice.
- “The action kind or type for call notes does not exist.” Set Action kind and Action type as they are named in onOffice.
- “The default agent was not found.” Enter the user name or ID of a user that onOffice lists for the API user.