Actions19
Overview
This node integrates with the Syncro RMM API to update customer information. It allows users to modify various details of an existing customer record, such as contact information, address, business name, notification preferences, and custom fields.
Common scenarios where this node is beneficial include:
- Automating updates to customer records when new information is received from other systems.
- Synchronizing customer data between Syncro RMM and external CRMs or databases.
- Managing customer communication preferences programmatically.
For example, you could use this node to update a customer's phone number and email address after receiving updated contact info from a web form submission.
Properties
| Name | Meaning |
|---|---|
| Customer ID | The unique identifier of the customer to update. |
| Customer Fields | A collection of optional fields to update for the customer: |
| - Address | Customer's address details including Line 1, Line 2, City, State, and ZIP code. |
| - Business Name | The business name associated with the customer. |
| - First Name | Customer's first name. |
| - Last Name | Customer's last name. |
| - Get SMS | Boolean flag indicating if the customer should receive SMS notifications. |
| - Invoice Emails | One or more email addresses to receive invoice copies (multiple values allowed). |
| - No Email | Boolean flag indicating if the customer should not receive emails. |
| - Notes | Additional notes about the customer. |
| - Notification Email | Email address to receive notifications (only used if "No Email" is false). |
| - Phone | Customer's phone number. |
| - Referred By | Source from which the customer was referred (e.g., LinkedIn, Google, another customer). |
| Customer's email address. | |
| Custom Fields | Multiple custom fields can be set by specifying the field name or ID and the value to assign. |
Output
The node outputs JSON data representing the updated customer object as returned by the Syncro RMM API. This typically includes all customer properties after the update, reflecting the changes made.
There is no indication that the node outputs binary data.
Dependencies
- Requires an active connection to the Syncro RMM API.
- Needs an API key credential configured in n8n for authentication.
- The base URL for API requests depends on the user's Syncro RMM subdomain.
- The node uses internal methods to load options dynamically, such as available custom fields.
Troubleshooting
- Invalid API Key: If the API key is incorrect or expired, the node will fail to authenticate. Ensure the API key credential is valid and has appropriate permissions.
- Customer Not Found: Providing an incorrect or non-existent Customer ID will result in errors. Verify the Customer ID before running the node.
- Validation Errors: Incorrectly formatted fields (e.g., invalid email format) may cause the API to reject the update. Double-check input formats.
- Notification Email Conflict: If "No Email" is set to true but a notification email is provided, the node hides the notification email field; ensure these settings are consistent.
- Custom Field Issues: When setting custom fields, ensure the field IDs or names exist and are accessible via the API.
Links and References
- Syncro RMM API Documentation (for detailed API endpoints and data models)
- n8n Expressions Documentation (for using expressions in field values)
