npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@gfynf/n8n-nodes-omahahomesforsale

v1.0.0

Published

n8n community node for the Omaha Homes For Sale CRM API. Manage leads, groups, agents, favorites, saved searches, notes, and more.

Downloads

74

Readme

n8n-nodes-omahahomesforsale

A custom n8n community node for the Omaha Homes For Sale CRM API. Connect your n8n workflows to your real estate CRM to manage leads, groups, favorites, saved searches, history events, notes, and more.


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-omahahomesforsale
  4. Click Install

Option B: Manual install on self-hosted n8n

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

Then restart n8n.

Option C: Install from this folder (development)

cd n8n-nodes-omahahomesforsale
npm install
npm run build
npm link

# In your n8n folder:
npm link n8n-nodes-omahahomesforsale

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 http://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 | | Favorite | Create, Get, Delete, List All | | History Event | Create (Action/FormSubmission, Phone calls) | | Saved Search | Create, Get, Update, Delete, List All | | Note | Create | | 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.
  • Groups field on leads: When updating group assignments, the groups field must contain ALL groups the lead should be in (not just new ones). Use a comma-separated list of group IDs.
  • 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.
  • Notes: The Create Note operation returns a success flag (the API returns 204 No Content on success).
  • Hooks: The Trigger Hook operation returns a success flag (the API returns 204 No Content on success).

API Reference

Full documentation: API Developer Reference

Authentication uses the X-REW-API-Key HTTP header.