estatesync

n8n community node for the EstateSync API: distribute real estate listings to German marketplaces (Immobilienscout24, Immowelt, Kleinanzeigen).

Package Information

Released: 4 mo ago
Downloads: 16 weekly / 42 monthly
Latest Version: 0.1.4
Author: Hans Doebel

Documentation


n8n-nodes-estatesync

NPM Version GitHub License NPM Downloads NPM Last Update Static Badge

Installation | Credentials | Resources | Development | License


A community node for n8n that integrates with the EstateSync API. EstateSync distributes real-estate listings to major German marketplaces (Immobilienscout24, Immowelt, Kleinanzeigen) — send your data once and publish on every platform.

API Coverage

The package ships two nodes covering the EstateSync REST API and webhook subscriptions:

  • EstateSync: action node covering all CRUD operations across 7 resources
  • EstateSync Trigger: webhook-based trigger that auto-registers a subscription with EstateSync and emits incoming events
View resources
Resource Operations
Account Get, Set Immobilienscout24 Credentials, Set Immobilienscout24 Sandbox Credentials
Contact Create, Delete, Get, List, Update
Listing Create, Delete, Get, List, Update
Property Create, Delete, Get, List, Update
Request Create, Get, List
Target Create, Delete, Get, List, Update
Webhook Create, Delete, List, Update
View trigger events
Event Type
Property Processing Succeeded Webhook
Property Processing Failed Webhook
Publication Succeeded Webhook
Publication Failed Webhook
Request Created Webhook
Request Parsing Failed Webhook

Installation

  1. Create a new workflow or open an existing one
  2. Open the nodes panel by selecting + or pressing N
  3. Search for EstateSync
  4. Select Install to install the node for your instance

Alternatively, follow the community node installation guide and install n8n-nodes-estatesync.

Credentials

  1. Sign up at EstateSync
  2. Manage and copy keys from the EstateSync dashboard
  3. In n8n, go to Credentials > Add credential
  4. Search for EstateSync API and paste your token

Every request is authenticated with Authorization: Bearer <key>. The credential's "Test" button hits GET /account to verify the key.

Resources & Operations

See the collapsible tables above under API Coverage for a full list.

List pagination

List endpoints (Contact, Listing, Property, Request, Webhook) accept Limit (1–100, default 10) and Start After (cursor — pass the ID of the last item from the previous page). Targets are returned as a non-paginated array.

Property and Target bodies

The property-new and target-new schemas are discriminated unions (one variant per property type or marketplace), so the Create and Update operations on these resources accept the body as a JSON parameter. See the EstateSync API reference for the per-type field list.

Trigger behavior

The EstateSync Trigger node manages its own webhook subscription:

  • On workflow activation, it calls POST /webhooks with the n8n-generated URL and the events you selected.
  • On deactivation, it calls DELETE /webhooks/{id} to clean up.
  • On every incoming delivery, it emits the JSON body — { eventId, eventName, eventPayload, eventTime } — into the workflow.

EstateSync retries non-2xx responses up to 8 times with exponential backoff. The trigger does not verify request signatures (EstateSync does not currently document a signing scheme).

Development

git clone https://github.com/hansdoebel/n8n-nodes-estatesync.git
cd n8n-nodes-estatesync
bun install
bun run build
bun run lint

License

MIT

GitHub | Issues | EstateSync API Docs

Discussion