OmahaHomesForSale icon

OmahaHomesForSale

Omaha Homes For Sale custom node
Join our community

Actions18

Overview

This node integrates with the Omaha Homes For Sale CRM API to manage saved searches associated with leads. Specifically, the "List All Saved Searches" operation retrieves all saved search records for a given lead identified by their email address. It supports optional filtering by IDX feed identifier, title, or search criteria.

This node is useful in scenarios where you want to programmatically access all saved property searches that a lead has created or subscribed to within the Omaha Homes For Sale system. For example, a real estate agent could use this node to fetch and display all saved searches of a client to tailor communications or update listings accordingly.

Properties

Name Meaning
Email The e-mail address of the lead whose saved searches are to be listed.
Additional Fields Optional filters to narrow down the list of saved searches:
- Feed The IDX feed identifier. If provided, only saved searches for this specific feed will be returned.
- Title The title of the saved search to filter by.
- Criteria The saved search criteria as a string of comma-separated key-value pairs (e.g., field1: value1, field2: value2).

Output

The output is a JSON array containing the saved search objects retrieved from the API for the specified lead. Each object represents a saved search with its details such as title, criteria, feed, source, frequency, and other metadata as defined by the Omaha Homes For Sale CRM.

No binary data is output by this operation.

Example output structure (simplified):

[
  {
    "id": "search_id_123",
    "title": "My Favorite Homes",
    "criteria": {
      "bedrooms": "3",
      "bathrooms": "2"
    },
    "feed": "feed_identifier",
    "source": "listings_table",
    "frequency": "weekly"
  },
  ...
]

Dependencies

  • Requires an API key credential for Omaha Homes For Sale API authentication.
  • The node makes HTTP requests to the base URL: http://www.omahahomesforsale.com/api/crm/v1.
  • The API key must be configured in n8n credentials and is sent in the header X-REW-API-Key.

Troubleshooting

  • Authentication errors (HTTP 400 or 401): Usually caused by missing or invalid API key. Verify that the API key credential is correctly set up and valid.
  • Empty results: If no saved searches are returned, check that the email address corresponds to an existing lead and that any additional filters (Feed, Title, Criteria) are correct.
  • Malformed criteria string: The criteria filter expects a comma-separated list of key-value pairs separated by colons. Incorrect formatting may cause the API to reject the request or return unexpected results.
  • Network issues: Ensure that the node can reach the Omaha Homes For Sale API endpoint and that there are no firewall or connectivity problems.

Links and References

  • Omaha Homes For Sale API documentation (if available publicly)
  • n8n HTTP Request node documentation for understanding how HTTP calls are made
  • General REST API best practices for troubleshooting API integration issues

Discussion