Actions18
- Favorites Actions
- Groups Actions
- History Events Actions
- Leads Actions
- Saved Searches Actions
Overview
The "List All Favorites" operation of the OmahaHomesForSale node retrieves a list of all favorite property listings associated with a specific lead, identified by their email address. This operation is useful for real estate agents or CRM users who want to quickly access and manage the saved favorite properties of a lead within the Lead Management system.
Typical use cases include:
- Displaying all favorite listings of a lead to understand their preferences.
- Syncing favorite listings data from the CRM to other systems.
- Filtering favorites based on certain listing attributes like feed, MLS number, or property type.
Example: An agent wants to see all the favorite homes saved by a particular lead to tailor follow-up communications or suggest similar properties.
Properties
| Name | Meaning |
|---|---|
| The e-mail address of the lead whose favorites are being listed. | |
| Additional Fields | Optional filters to narrow down the favorites list: |
| - Feed | The IDX feed identifier of the listing. |
| - MLS number | The MLS number of the listing within the IDX feed. |
| - Type | The property type of the listing within the IDX feed. |
Output
The output is a JSON array containing the response from the API call that lists the favorite listings for the specified lead. Each item in the array represents a favorite listing object with details as returned by the external service.
If an error occurs (e.g., invalid parameters or authentication issues), the output will contain an error object describing the problem.
No binary data is produced by this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Omaha Homes For Sale API.
- The node makes HTTP GET requests to the endpoint:
http://www.omahahomesforsale.com/api/crm/v1/leads/{email}/favorites - The API key must be provided in the request header
"X-REW-API-Key".
Troubleshooting
Common Issues:
- Invalid or missing email parameter will cause the API to reject the request.
- Incorrect or expired API key will result in authentication errors.
- Providing invalid filter values in additional fields may cause the API to return errors or empty results.
Error Messages:
- HTTP 400 Bad Request: Usually indicates malformed input or missing required parameters.
- HTTP 401 Unauthorized: Indicates invalid or missing API key.
- Error responses from the API are passed through in the output; check the error message for details.
Resolution Tips:
- Ensure the email address is correctly formatted and corresponds to an existing lead.
- Verify that the API key credential is valid and has necessary permissions.
- Use only supported values for filters like feed, MLS number, and type.
Links and References
- Omaha Homes For Sale API documentation (if available) would provide detailed information about the favorites endpoint and expected response structure.
- n8n documentation on creating and using credentials for API authentication.