Actions36
- Activity Actions
- Contact Actions
- Customer Actions
- Data Proxy Actions
- Document Actions
- Employer Actions
- Lead Actions
- Meeting Actions
- Meeting Summary Actions
- Report Actions
- Workflow Actions
Lead → Update a Lead
AI-generatedOverview
The "Update a Lead" operation in this node allows users to modify the details of an existing lead within the Surense system. This is useful for keeping lead information current, such as updating contact details, status, priority, or other relevant attributes. Practical scenarios include changing the lead's owner after reassignment, updating notes following a conversation, or marking a lead as closed with a reason.
Properties
| Name | Meaning |
|---|---|
| Lead ID | The unique identifier (UUID format) of the lead to update. |
| Additional Parameters | A collection of optional fields to update various aspects of the lead: |
| - Pinned | Whether the lead is pinned (boolean). |
| - Priority | Lead priority level; options are "1", "2", or "3". |
| - Notes | Text notes about the lead. |
| - Closed Reason | Reason for closing the lead. |
| - Type Name or ID | Lead type, selectable from a list or specified by ID via expression. |
| - Status Name or ID | Lead status, selectable from a list or specified by ID via expression. |
| - Agency Name or ID | Associated agency, selectable from a list or specified by ID via expression. |
| - Owner Name or ID | Lead owner, selectable from a list or specified by ID via expression. |
| - Assignee Name or ID | Assigned user, selectable from a list or specified by ID via expression. |
| - Source Name or ID | Lead source, selectable from a list or specified by ID via expression. |
| - Lead Date | Date associated with the lead (format YYYY-MM-DD). |
| - Due At | Due date and time for the lead. |
| - Due At Time Set | Boolean indicating whether the due time is set. |
| - First Name | Lead's first name. |
| - Last Name | Lead's last name. |
| - סוג מזהה לקוח (ID Type) | Type of customer ID; options include ת.ז (1), דרכון (2), רישיון נהיגה (3), אחר (4). |
| - ID Number | Customer ID number. |
| - ID Card Issue Date | Issue date of the ID card (format YYYY-MM-DD). |
| - Cell Number | Cell phone number. |
| - Phone Number | General phone number. |
| - Phone Number 1 | Primary phone number. |
| - Phone Number 2 | Secondary phone number. |
| Email address. | |
| - Street | Street name. |
| - Street Number | Street number (numeric). |
| - Apartment Number | Apartment number (numeric). |
| - Postal Box | Postal box number (numeric). |
| - City | City name. |
| - Postal Code | Postal code (numeric). |
| - Country | Country name. |
| - Gender | Gender; options are זכר (2) or נקבה (3). |
| - Birth Date | Birth date (format YYYY-MM-DD). |
| - Age | Age (numeric). |
| - Deceased | Whether the person is deceased (boolean). |
| - Marital Status | Marital status; options include רווק (1), נשוי (2), גרוש (3), אלמן (4), ידוע בציבור (5). |
| - Smoker | Whether the person is a smoker (boolean). |
| - Number of Children | Number of children (numeric). |
| - Monthly Income | Monthly income (numeric). |
| - Employer Name | Employer's name. |
| - Meeting Date | Date of meeting (format YYYY-MM-DD). |
| - Meeting Time | Time of meeting (string, e.g., "HH:MM"). |
| - Meeting Location | Location of the meeting. |
| - Meeting Coordinator Name or ID | Meeting coordinator, selectable from a list or specified by ID via expression. |
Output
The node outputs JSON data representing the updated lead object as returned by the Surense API. This typically includes all the lead's properties reflecting the new state after the update operation. There is no indication that binary data is output by this operation.
Dependencies
- Requires an active connection to the Surense API.
- Requires an API authentication token configured in n8n credentials (an OAuth2 or similar API key credential).
- Uses dynamic option loading methods to populate dropdowns for agencies, users, lead types, statuses, sources, etc., which depend on successful API communication.
Troubleshooting
- Common Issues:
- Invalid or missing Lead ID will cause the update to fail.
- Providing invalid values for enumerated fields (e.g., priority, gender, marital status) may result in errors.
- Network or authentication issues with the Surense API can prevent operation execution.
- Error Messages:
- Errors related to "Lead not found" indicate the Lead ID does not exist.
- Authentication errors suggest misconfigured or expired API credentials.
- Validation errors may occur if required fields are missing or contain invalid data formats.
- Resolutions:
- Verify the Lead ID is correct and exists in the system.
- Ensure API credentials are valid and have necessary permissions.
- Double-check input property values against allowed options and formats.
Links and References
- n8n Expressions Documentation
- Surense API documentation (not provided here; consult your Surense API docs for detailed field descriptions and API usage)