OmahaHomesForSale icon

OmahaHomesForSale

Omaha Homes For Sale custom node
Join our community

Actions18

Overview

This node interacts with the Omaha Homes For Sale Lead Management API, specifically managing "Favorites" related to leads. The Delete Favorite operation allows users to delete a favorite listing associated with a specific lead by providing the lead's email and the favorite record's identifier. This is useful for cleaning up or managing a lead’s saved favorite properties in the system.

Practical example: If a real estate agent wants to remove a property from a lead’s list of favorites (perhaps because the property is no longer available or relevant), this node operation can be used to delete that favorite entry programmatically.

Properties

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

Output

The output JSON contains the response from the API after attempting to delete the favorite. Typically, it will include confirmation of deletion or error details if the operation failed.

Example output structure:

{
  "response": {
    // API response confirming deletion or empty object
  }
}

If an error occurs (e.g., invalid ID or unauthorized access), the output will contain an error message and possibly additional error details.

Dependencies

  • Requires an API key credential for authentication with the Omaha Homes For Sale API.
  • The node makes HTTP DELETE requests to the endpoint structured as:
    http://www.omahahomesforsale.com/api/crm/v1/leads/{email}/favorites/{id}
  • The API key must be provided in the request header X-REW-API-Key.
  • No other external dependencies are required.

Troubleshooting

  • Common issues:

    • Invalid or missing email or favorite ID parameters will cause the API to reject the request.
    • Unauthorized errors if the API key is missing, invalid, or expired.
    • Network connectivity issues preventing communication with the API endpoint.

  • Error messages:

    • HTTP 400 Bad Request: Usually indicates missing or malformed parameters. Verify that the email and favorite ID are correct.
    • HTTP 401 Unauthorized: Indicates an issue with the API key credential. Ensure the API key is valid and correctly configured in n8n.
    • Other errors may include detailed messages from the API in the response body; these should be reviewed to understand the failure reason.

  • Resolution tips:

    • Double-check input values for correctness.
    • Confirm API key validity and permissions.
    • Check network connectivity and firewall settings.
    • Enable "Continue On Fail" in the node settings to handle errors gracefully during workflow execution.

Links and References

Discussion