rew-crm

n8n community node for the Omaha Homes For Sale CRM API (Real Estate Webmasters). Manage leads, groups, sources, agents, favorites, saved searches, notes, webhook subscriptions, and more.

Package Information

Released: this month
Downloads: 13 weekly / 31 monthly
Latest Version: 1.1.1
Author: Ryan Renner

Available Nodes

Omaha Homes For Sale CRM icon
Omaha Homes For Sale CRM
Interact with the Omaha Homes For Sale CRM API to manage leads, groups, agents, and more

Documentation

n8n-nodes-rew-crm

An n8n community node for the Omaha Homes For Sale CRM API (Real Estate Webmasters). Connect your n8n workflows to your real estate CRM to manage leads, groups, sources, favorites, saved searches, history events, notes, webhook subscriptions, and more.

The node can also be used as a tool by n8n AI Agents.

Installation

Option A: Install via n8n Community Nodes (Recommended)

  1. In your n8n instance, go to Settings > Community Nodes
  2. Click Install
  3. Enter the package name: n8n-nodes-rew-crm
  4. Click Install

Option B: Manual install on self-hosted n8n

# In your n8n root or custom nodes directory:
npm install n8n-nodes-rew-crm

Then restart n8n.

Option C: Run from this folder (development)

npm install
npm run dev   # starts a local n8n with this node loaded, rebuilding on change

Credentials Setup

  1. In n8n, go to Credentials > New
  2. Search for Omaha Homes For Sale CRM API
  3. Enter your API Key (sent via X-REW-API-Key header)
  4. The Base URL defaults to https://www.omahahomesforsale.com/api/crm/v1. Only change this if needed
  5. Click Save. n8n will test the credentials automatically using the /agents endpoint

Supported Resources & Operations

Resource Operations
Lead Create, Get, Update, Create or Update (Upsert)
Agent List All
Group Create, Get, Delete, List All
Source Create, List All
Favorite Create, Get, Delete, List All
History Event Create (Action/FormSubmission, Phone calls)
Saved Search Create, Get, Update, Delete, List All
Note Create
Subscription (Webhook) Create, Get, Update, Delete, List All
Hook Trigger (rew.lead.text.incoming)

Usage Notes

  • Lead email is the unique identifier for leads throughout the API. You cannot change a lead's email via the API.
  • Group IDs / Source IDs on leads are comma-separated lists of IDs (e.g. 154,168). When updating a lead's groups, the list must contain ALL groups the lead should be in, not just new ones. Source IDs can be set on Create and Create or Update.
  • Quick Note is the short message shown on the lead results and details pages. The older Comments field is deprecated by REW.
  • Blank values are ignored on update. The API leaves a field unchanged if you send it empty, so fields can't be cleared through the API.
  • Group name filter is an exact match: PEND will not find a group named - PEND.
  • Lead Upsert: Use "Create or Update" to safely sync leads from external systems. It creates the lead if it doesn't exist, or updates it if it does.
  • Subscriptions register a webhook URL that the CRM calls on lead.created or lead.updated. Pair one with an n8n Webhook node to react to CRM changes instead of polling. The target receives real lead data, so only point it at URLs you control.
  • Notes and Hooks return a success flag, since the API returns no useful payload for them.

API Reference

Authentication uses the X-REW-API-Key HTTP header. The full API reference is available from your REW site's API documentation page.

Development

npm run lint    # n8n's community node linter
npm run build   # compile to dist/

npm publish runs lint and build first, so a package that fails either is never published.

Discussion