propstack
With the propstack integration, propstack remains the system of record. deep.rent does not bulk-import the CRM. Contact and object pickers search propstack live; only when you select a result is that entity copied into deep.rent.
Flow: search live → pick a result → copy that one entity → attach it to a protocol or object. Local lists only contain what your organisation actually used — even for very large CRMs.
Requirements
- An active deep.rent account
- An active propstack account
- Internet connection during setup and when using search
What the connector does
| Capability | What you get |
|---|---|
| Live contact search | Full-text over name, emails, address and phones (optional email / phone filters) |
| Live object search | Full-text over units; inactive (“Inaktiv”) units are hidden |
| On-demand copy | Selecting a hit creates or updates the matching deep.rent contact or object (objects also bring linked contacts and address) |
| Refresh | Re-sync only already-copied rows — never pulls in new CRM records automatically |
| PDF upload | Upload a protocol PDF to the propstack property under Media/Documents |
| Credentials | Organisation API key stored encrypted; connection test via integrations settings |
Copied data typically includes:
- General object data (e.g. address, area, status)
- General contact data (e.g. name, email, phone)
- Relationships between objects and contacts (e.g. owner, tenant) when present in propstack
Technical notes
- The Propstack API key is processed server-side only and stored encrypted (encryption at rest). It is not exposed to the client or third parties.
- All Propstack access goes through secured backend endpoints. There is no direct client-to-Propstack communication.
- The integration uses least-privilege permissions:
- Read objects and contacts
- Write (upload) documents
- No delete or modification of existing Propstack data
- Sensitive data (e.g. API keys) is not written to logs or stored in plain text.
- Access is organisation-scoped and protected by authentication and role checks (e.g. admin/owner).
- All external connections use HTTPS.
- Detail requests and copying individual entities run only when needed (data minimisation).
- Error and status messages do not expose confidential data (no API keys or raw payloads).
Setup in propstack
Create an API key
- In propstack, open Administration.
- Go to Menu > API keys.
- Add the key from the selection (deeprent) or create a new key with:
- Read access for Objects and Contacts
- Write access for Documents
Contact statuses for mapping
Under Administration > Contact settings, these contact statuses should exist (used for mapping). Add Tenant if you use it:
- Owner
- Tenant
- Contact
- Authority
- Lawyer, notary
- Service provider
- Business partner
- Buyer
- Purchase prospect
- Seller
- Seller lead
- Cold lead
Setup in the Protocol app
- Open Settings → Integrations in the app.
- Select propstack.
- Enter the propstack API key.
- Confirm or test the connection.
No bulk import is required or available. Contacts and objects are available through live search in the pickers.
After connecting
- Search contacts and objects live in propstack and select the hit you need — only then is it copied into deep.rent.
- Already-copied rows can be refreshed later; new CRM records appear only when you select them.
- Use copied objects and contacts to create protocols.
- Finished protocols can be uploaded as PDFs to the related object in propstack.
Troubleshooting
- Connection failed: Check the API key and permissions in propstack, then reconnect.
- No search results: Check the search term; in propstack, verify the record exists and (for objects) is not inactive.
- Incomplete data: Check read permissions for objects and contacts, and contact statuses in propstack.
- PDF upload failed: Check write access for documents on the API key.