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 "Delete a Saved Search" operation allows users to delete a saved search record by its identifier for a given lead's email address. This is useful in scenarios where a lead no longer wants to receive alerts or notifications related to a particular saved search, or when cleaning up outdated or irrelevant saved searches.

Practical examples:

  • Automatically removing saved searches when a lead unsubscribes from alerts.
  • Cleaning up saved searches that are no longer valid after a lead updates their preferences.
  • Managing saved searches programmatically as part of a lead lifecycle automation.

Properties

Name Meaning
Email The e-mail address of the lead whose saved search you want to delete.
Id The unique identifier of the saved search record to be deleted.

Output

The output JSON contains the response from the API after attempting to delete the saved search. Typically, this will be an object indicating success or failure of the deletion request. If successful, it may be an empty object or confirmation message. In case of failure, the output includes error details explaining why the deletion failed.

No binary data is output by this operation.

Example output on success:

{}

Example output on failure:

{
  "success": false,
  "error": "Error message describing the issue"
}

Dependencies

  • Requires an API key credential for authentication with the Omaha Homes For Sale CRM API.
  • The node makes HTTP DELETE requests to the endpoint:
    http://www.omahahomesforsale.com/api/crm/v1/leads/{email}/searches/{id}
  • Proper configuration of the API key credential in n8n is necessary.
  • The node expects the base URL and headers to be set as per the bundled code.

Troubleshooting

  • Common issues:

    • Invalid or missing API key: The API will respond with 401 Unauthorized errors.
    • Incorrect email or saved search ID: The API may return 400 Bad Request or 404 Not Found errors if the specified lead or saved search does not exist.
    • Network connectivity problems can cause request failures.

  • Error messages and resolutions:

    • "success": false, "error": "Invalid API key": Verify that the API key credential is correctly configured and active.
    • "success": false, "error": "Saved search not found": Confirm that the saved search ID and email correspond to an existing saved search.
    • HTTP 400 or 401 errors: Check input parameters and credentials; ensure all required fields are provided and valid.

  • Enable "Continue On Fail" in the node settings to handle errors gracefully within workflows.

Links and References

Discussion