Quick answer
In 2026, onOffice and Propstack can both be connected to Make or n8n through their REST APIs — onOffice via the onOffice API with HMAC signature, Propstack via its REST API with an API key. This lets agencies automate the full cycle: lead capture from the website and portals, property sync to ImmoScout24 and Kleinanzeigen, AI-generated exposé copy and reply drafts, plus reporting. Make suits fast, low-maintenance standard flows; n8n is worth it when you need data sovereignty, self-hosting and complex logic — and when you want to own the system yourself.
What is worth automating
The biggest time drains in an agency office are recurring data transfers and first contacts. In practice, teams typically automate:
- Lead routing: enquiries from website forms, ImmoScout24, Kleinanzeigen and Meta lead ads land automatically as a contact/prospect in the CRM — with a source tag and property reference.
- Property distribution: new or changed properties from onOffice/Propstack are pushed out to portals, your own website and the newsletter.
- AI enrichment: exposé copy, social posts and reply drafts are generated by an LLM (OpenAI, Claude, Azure OpenAI) and written back into the CRM for approval.
- Follow-up & nurturing: time-triggered reminders, viewing appointment suggestions and no-response checks.
- Reporting: daily or weekly metrics (leads per source, response time, active listings) into a dashboard or Slack/Teams.
The decisive point: automate the process with the highest volume and the clearest rule first — usually lead routing.
API basics: onOffice vs. Propstack
onOffice enterprise API
The onOffice API works with a token/secret pair and requires an HMAC-SHA256 signature over the action parameters for every request. That is secure, but not trivial: in Make you usually rebuild the HMAC with an HTTP module plus an upstream signature step in a setup without custom JS; in n8n you use the Crypto node together with an HTTP Request node. The API covers addresses (contacts), estates (properties), activities and search criteria. Permissions are enabled per token in the onOffice Marketplace — clarify API access early with your onOffice contact.
Propstack API
Propstack offers a more modern REST API with simple API key authentication in the header and JSON payloads. Endpoints exist for contacts, properties, deals/projects and activities. The lower barrier to entry makes Propstack faster to connect in Make/n8n; watch the rate limits and use webhooks instead of polling wherever they are available.
The practical difference
For a Make/n8n project, the rule of thumb for 2026 is: Propstack integrates faster, because there is no signature overhead; onOffice requires more setup effort, but is already established as the data hub in many DACH offices. Both work reliably as long as you handle rate limits and error handling cleanly.
Make or n8n? The build decision
| Criterion | Make | n8n |
|---|---|---|
| Getting started | Very fast, many ready-made modules | Steeper, more building yourself |
| HMAC/custom logic | More cumbersome | Native via code/crypto node |
| Hosting & data sovereignty | Cloud (EU region selectable) | Cloud or self-hosted (GDPR-friendly) |
| Cost model | Per operation | Per execution / self-host flat |
| Maintenance | Vendor-dependent | The team owns the system |
Choose Make if you need a handful of clear flows, want to go live fast and don't need deep custom logic. Choose n8n if data protection, self-hosting on an EU/German server, complex branching or high execution volumes are involved — or if your team is meant to run the system itself long term. In practice, many DACH agencies combine both: Make for standard marketing flows, self-hosted n8n for the data-sensitive CRM core logic.
Concrete workflow recipes
1. Portal & website lead into the CRM (in under 30 seconds)
- 1Trigger: webhook from the website form (e.g. Softr/WordPress) or an email parser for portal enquiries (ImmoScout24 and Kleinanzeigen send lead emails).
- 2Normalise: map name, email, phone, property ID and source into a single unified field schema.
- 3Duplicate check: search for the contact by email/phone in onOffice/Propstack.
- 4Write: create a new contact or update the existing one, and log a "portal enquiry" activity with the source tag.
- 5Notify: inform the responsible agent via Slack/Teams/email — including the property link.
Result: no enquiry gets lost, and response time often drops from hours to minutes — the single most important lever for your conversion rate.
2. Property sync CRM → website
- Trigger: new/changed property (webhook or scheduled polling of the properties endpoints).
- Transform: map fields into your website schema (title, price, floor area, rooms, mandatory energy certificate details).
- Target: write into an Airtable database or directly into a Softr CMS that renders your property website.
- Images: carry over media URLs; add watermarking/resizing in an intermediate step if needed.
This way agencies maintain properties once in the CRM and the website stays up to date automatically.
3. AI exposé copy & reply draft
- Send property data (location, features, floor area) to an LLM as a structured prompt.
- Response: exposé copy, three social media variants and a reply draft for the portal enquiry.
- Important: write the result into the CRM activity field as a draft, don't send it automatically. The agent approves it. That protects quality and compliance.
- Keep mandatory details (energy certificate, commission) outside the LLM in fixed text blocks to avoid errors.
4. Daily reporting
A nightly flow pulls leads per source, open tasks and response times and posts a compact overview to Slack/Teams or into an ops dashboard (for example on Softr). That gives management control without manual Excel work.
Implementation in 6 steps
- 1Process map: note the 5–8 recurring workflows and their volume. Prioritise by time saved × frequency.
- 2Clarify API access: request the onOffice token/secret via the Marketplace, generate the Propstack API key. Set permissions minimal, but sufficient.
- 3Define the field schema: one unified internal data model (contact, property, activity, source) as the reference for all flows.
- 4Build the first flow: start with lead routing — highest benefit, clearest rules.
- 5Error handling & logging: retry on rate limits, error notifications, a log sheet for every execution.
- 6Handover & ownership: documentation, access management and training, so that your team owns the system and isn't dependent on a single service provider.
Common mistakes and how to avoid them
- Fully automated AI sending: always require human approval for customer communication.
- Polling instead of webhooks: wastes operations/executions and time — prefer webhooks.
- No duplicate check: leads to duplicate contacts and confuses the sales team.
- Ignoring GDPR: process personal data in the EU (Make EU region or n8n self-hosted on a German server), sign data processing agreements with all services, keep prompts data-minimal.
- No monitoring: without error alerts, a silent outage is only noticed when leads are missing.
No-code vs. custom build: where is the line?
Make/n8n plus onOffice/Propstack covers 80–90% of automation needs. An individual custom build (for example a client or partner portal on Softr with an Airtable backend) is worth it when you need an interface for owners, prospects or partners that the CRM doesn't offer — such as an owner dashboard with marketing status, viewing feedback and documents. The rule: automation connects systems, a portal creates a new interface. The two work together — the portal shows the data that the automation keeps current.
FAQ
Do I need programming skills to connect onOffice with Make?
For Propstack, no-code skills are usually enough. For onOffice, a basic technical understanding is required because of the HMAC signature; in n8n the signature can be built cleanly with the Crypto node. Many offices have the core set up once and then maintain it themselves.
Is the automation GDPR-compliant?
Yes, if you process data in the EU (Make EU region or n8n self-hosted on a German/EU server), sign data processing agreements with all services involved, and pass only the necessary data into AI prompts. Minimise or anonymise personal data in LLM prompts wherever possible.
What does such a setup cost in 2026?
Tool costs are moderate: Make from roughly €10–30 per month depending on operation volume, self-hosted n8n practically only server cost (€5–20 per month), LLM usage on consumption. The main effort lies in the one-off setup and in clean process definition.
Can I run onOffice and Propstack in parallel?
Technically yes — during a migration, for instance. But it makes sense to have one system as the "single source of truth". Automation can secure the transition phase by keeping data synchronised in one direction.
What is the fastest way to start?
Start with a single flow — lead routing from the website and one portal into the CRM. That one process delivers immediately measurable value (faster response time) and is the template for all further automations.
Conclusion
onOffice and Propstack are solid automation foundations in 2026: Propstack integrates faster, onOffice takes a bit more setup but is deeply established. With Make, standard flows go live in days; with n8n you get data sovereignty and full control over complex logic. What matters is not the tool, but process prioritisation, clean error handling — and that your team owns the system in the end.