OmahaHomesForSale icon

OmahaHomesForSale

Omaha Homes For Sale custom node
Join our community

Actions18

Overview

This node allows users to create a new saved search associated with a lead in a real estate CRM system. It is useful for automating the management of property searches that leads are interested in, enabling timely notifications and personalized follow-ups based on saved criteria.

Typical scenarios include:

  • Automatically creating saved property searches for leads based on their preferences.
  • Setting up email alert frequencies for saved searches to keep leads informed about new listings.
  • Integrating saved search creation into lead nurturing workflows.

For example, a real estate agent can use this node to save a search for a lead looking for 3-bedroom homes in a specific neighborhood, specifying how often the lead should receive email alerts about matching properties.

Properties

Name Meaning
Email The e-mail address of the lead to associate the saved search with.
Title The title or name of the saved search.
Criteria The search criteria as a string of comma-separated key-value pairs (e.g., field1: value1, field2: value2). These define the parameters of the saved search.
Feed The IDX feed identifier that the search applies to.
Source The table within the IDX database to be searched.
Additional Fields A collection of optional fields; currently supports:
- Frequency: The frequency of email alerts for the search. Accepted values: never, daily, weekly, monthly. Defaults to weekly if not specified.

Output

The node outputs an array of JSON objects representing the response from the API after creating the saved search. The structure typically includes details of the newly created saved search such as its identifier, title, criteria, feed, source, and alert frequency.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authentication with the Omaha Homes For Sale CRM API.
  • The base URL for API requests is 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 key will result in authentication errors.
    • Incorrectly formatted criteria string may cause the API to reject the request.
    • Missing required fields like email, title, feed, or source will cause validation errors.

  • Error messages:

    • HTTP 400 or 401 responses usually indicate bad requests or unauthorized access. The error message from the API will be included in the output.
    • Network or unexpected errors will throw exceptions unless "Continue On Fail" is enabled, in which case the error message is returned in the output.

  • Resolution tips:

    • Ensure all required fields are provided and correctly formatted.
    • Verify the API key is valid and has appropriate permissions.
    • Use the exact accepted values for fields like frequency to avoid validation errors.

Links and References

Discussion