OmahaHomesForSale icon

OmahaHomesForSale

Omaha Homes For Sale custom node
Join our community

Actions18

Overview

This node allows you to update an existing saved search associated with a lead in the Omaha Homes For Sale Lead Management system. It is useful when you want to modify the parameters of a saved search, such as its title, criteria, or email alert frequency, without creating a new one.

Typical scenarios include:

  • Adjusting the search criteria for a lead’s saved search to better match their preferences.
  • Changing the frequency of email alerts sent to the lead about new listings matching their saved search.
  • Renaming the saved search for clarity or organizational purposes.

For example, if a lead wants to receive daily updates instead of weekly, you can use this node to update the "Frequency" property accordingly.

Properties

Name Meaning
Email The e-mail address of the lead who owns the saved search.
Id The unique identifier of the saved search record to update.
Additional Fields Optional fields to update on the saved search:
- Frequency The frequency of email alerts for the search. Accepted values: never, daily, weekly, monthly. Defaults to weekly if not specified.
- Title The title/name of the saved search.
- Criteria The saved search criteria expressed as a string of comma-separated key-value pairs. Example: field1: value1, field2: value2.

Output

The node outputs a JSON array where each element corresponds to the response from updating a saved search. The structure typically contains the updated saved search object returned by the API or an error object if the update failed.

Example output JSON snippet:

[
  {
    "id": "12345",
    "title": "Updated Search Title",
    "criteria": {
      "field1": "value1",
      "field2": "value2"
    },
    "frequency": "daily",
    ...
  }
]

No binary data is produced by this node.

Dependencies

  • Requires an API authentication token credential to access the Omaha Homes For Sale Lead Management API.
  • The base URL for API requests is http://www.omahahomesforsale.com/api/crm/v1.
  • The node uses HTTP POST requests to update saved searches at endpoint /leads/{email}/searches/{id}.
  • Proper configuration of the API key credential in n8n is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing API token will cause authentication errors.
    • Providing an incorrect saved search ID or lead email may result in "not found" errors.
    • Malformed criteria string (not properly formatted as comma-separated key-value pairs) may cause the API to reject the request.

  • Error messages:

    • HTTP 400 or 401 responses usually indicate bad request or unauthorized access. Check that the API token is valid and that required parameters are correctly set.
    • Error messages from the API are included in the output to help diagnose issues.

  • Resolution tips:

    • Verify the lead's email and saved search ID exist in the system before attempting an update.
    • Ensure the criteria string follows the expected format: <key>: <value>, <key2>: <value2>.
    • Confirm the API token credential is correctly configured and has sufficient permissions.

Links and References

  • Omaha Homes For Sale Lead Management API documentation (if available) should be consulted for detailed information on saved search properties and accepted values.
  • n8n documentation on creating and using credentials for API authentication.

Discussion