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
Customer → Update
AI-generatedOverview
The node named "Surense" provides an interface to interact with the Surense API, supporting multiple resources and operations. Specifically for the Customer resource with the Update operation, this node allows users to update detailed information about a customer in the Surense system. This is useful in scenarios where customer data needs to be kept current, such as updating contact details, status, personal information, or other attributes after receiving new data from forms, CRM systems, or other integrations.
Practical examples include:
- Updating a customer's contact information after they submit a change request.
- Modifying customer status or classification based on recent interactions.
- Recording changes in personal details like marital status, employment, or health-related information.
Properties
| Name | Meaning |
|---|---|
| Customer ID | UUID of the customer to update (required). |
| Additional Parameters | A collection of optional fields to update various customer attributes: - Status Name or ID - Agency Name or ID - Class Name or ID - Source Name or ID - First Name - Last Name - English First Name - English Last Name - Short Name - Maiden Name - Gender (options: זכר (male), נקבה (female)) - Birth Date - Deceased (boolean) - Death Date - Marital Status (options: רווק (single), נשוי (married), גרוש (divorced), אלמן (widowed), ידוע בציבור (common-law)) - ID Number - ID Card Issue Date - Cell Number - Phone Number - Fax Number - Other Email - Street - Street Number - Postal Box - City - Postal Code - Country - English Address - Mailing Status (options: אושר דיוור (approved mailing), לא אושר דיוור (not approved mailing), הוסר מדיוור (removed from mailing), לא התבקש אישור (no approval requested)) - Employment Status (options: שכיר (employee), עצמאי (self-employed), שכיר ועצמאי (both), בעל שליטה (owner), לא מועסק (unemployed)) - Profession - Kupat Holim (health fund) (options: כללית, מכבי, מאוחדת, לאומית, צהלי״ת) - Kupat Holim Complementary (complementary health fund) - Height (cm) - Weight (kg) - Smoker (options: מעשן (smoker), לא מעשן (non-smoker)) - Cigarettes Per Day - Drugs - Hospitalizations - Surgeries - Background Diseases - Foreign Tax Residency (boolean) - US Citizen (boolean) - Notes - Notes Alert (boolean) |
Output
The node outputs an array of JSON objects representing the results of the update operation for each input item. Each output item contains the updated customer data as returned by the Surense API. If the operation fails and "Continue On Fail" is enabled, the output will contain an error message object instead.
The node does not explicitly handle binary data output.
Dependencies
- Requires an OAuth2 API credential configured for authenticating with the Surense API.
- The node depends on several helper modules and methods internally to load options dynamically for dropdowns (e.g., customer statuses, agencies, classes).
- Pagination support is included but not specifically relevant for the update operation.
Troubleshooting
- Common issues:
- Invalid or missing Customer ID will cause the update to fail.
- Providing invalid option values (e.g., IDs that do not exist) may result in API errors.
- Network or authentication failures due to incorrect or expired API credentials.
- Error messages:
- Errors thrown by the Surense API are caught and can be output as JSON error messages if "Continue On Fail" is enabled.
- Typical errors might include "Customer not found", "Invalid parameter", or "Authentication failed".
- Resolution tips:
- Ensure the Customer ID is correct and exists in the system.
- Verify all option values correspond to valid entries in Surense.
- Check and refresh API credentials if authentication errors occur.
Links and References
- n8n Expressions Documentation — for using expressions in property fields.
- Surense API documentation (not provided here) would be essential for understanding specific field requirements and constraints.