OmahaHomesForSaleInstall

Overview

This node interacts with the Omaha Homes For Sale CRM API to manage saved searches associated with leads. Specifically, the "Retrieve an Existing Saved Search" operation allows users to fetch details of a single saved search by its unique identifier for a given lead's email address.

Common scenarios where this node is beneficial include:

• Verifying if a particular saved search exists for a lead.
• Fetching saved search criteria and metadata to display or process further in workflows.
• Integrating saved search data retrieval into automated lead management or notification systems.

Practical example:

• A real estate agent wants to check the details of a saved search that a lead has created to tailor communications or update the lead’s profile accordingly.

Properties

Output

The output JSON contains the retrieved saved search object as returned by the Omaha Homes For Sale API. This typically includes fields such as:

• title: The title of the saved search.
• criteria: An object representing the search criteria as key-value pairs.
• feed: The IDX feed identifier related to the saved search.
• source: The database table within the IDX system that the search targets.
• Other metadata fields as provided by the API.

The output is structured as an array of JSON objects, each representing one saved search record (in this case, a single object).

No binary data is output by this operation.

Dependencies

• Requires an API authentication token credential for the Omaha Homes For Sale API.
• The node makes HTTP requests to the base URL: http://www.omahahomesforsale.com/api/crm/v1.
• Proper configuration of the API key credential in n8n is necessary for successful requests.

Troubleshooting

• Common issues:

  • Invalid or missing API token will cause authentication failures.
  • Providing an incorrect or non-existent saved search ID will result in errors or empty responses.
  • Incorrect email address format or a lead not existing in the system may cause the request to fail.

• Error messages:

  • HTTP 400 or 401 status codes indicate bad requests or unauthorized access, often due to invalid parameters or credentials.
  • Error responses from the API are included in the output to help diagnose issues.

• Resolution tips:

  • Verify the API token is correctly set and active.
  • Double-check the saved search ID and lead email for correctness.
  • Ensure the lead exists in the system before attempting to retrieve saved searches.

Links and References

• Omaha Homes For Sale API documentation (if available) would be the primary reference for detailed field descriptions and additional operations.
• n8n documentation on creating and using custom nodes and managing credentials.