OmahaHomesForSale icon

OmahaHomesForSale

Omaha Homes For Sale custom node
Join our community

Actions18

Overview

This node allows you to create a new history event associated with a lead in the Lead Management system. It is useful for tracking interactions or activities related to leads, such as form submissions or phone calls. Once created, these events appear in the Lead Manager under the lead's History tab, providing a timeline of actions and communications.

Practical examples include:

  • Logging when a lead submits a contact form on your website.
  • Recording details about phone calls made to or from a lead, including call attempts, contacts, voicemails, or invalid calls.

Properties

Name Meaning
Email The e-mail address of the lead to associate the event with.
Type The type of event. Options: Action (e.g., form submission) or Phone (phone call related event).
Sub Type The subtype of the event, dependent on the selected Type:
- For Action: Form Submission
- For Phone: Attempt, Contact, Invalid, Voicemail
Page (Required if Type is Action) The absolute URL of the page where the form submission occurred.
Form (Required if Type is Action) The name of the form that was submitted.
Form Fields (Required if Type is Action) Comma-separated key-value pairs representing form field names and values. Example: field1: value1, field2: value2
Details (Required if Type is Phone) Information related to the phone call, such as call notes or status.

Output

The node outputs a JSON object representing the response from the Lead Management API after creating the event. This typically includes confirmation details of the newly created event, such as its identifier and stored data.

No binary data output 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.
  • Proper configuration of the API key credential within n8n is necessary for successful requests.

Troubleshooting

  • Common issues:

    • Missing required fields such as Email, Type, or subtype-specific required properties (Page, Form, Form Fields for Action; Details for Phone).
    • Incorrect formatting of the Form Fields string (should be comma-separated key:value pairs).
    • Invalid or expired API token leading to authentication errors.
    • Network connectivity issues preventing API communication.

  • Error messages:

    • HTTP 400 or 401 errors usually indicate bad request parameters or authentication failure. Verify all required fields are correctly set and the API token is valid.
    • Error responses from the API will be included in the node output to help diagnose issues.

Links and References

Discussion