Actions19
Overview
The node integrates with the Syncro RMM API to manage customer data. Specifically, the "Customer" resource with the "Get Many" operation allows users to retrieve multiple customer records from Syncro RMM. This is useful for scenarios where you want to list customers, filter them by various criteria, or process batches of customer data for reporting, synchronization, or automation workflows.
Practical examples include:
- Fetching all customers to sync with a CRM system.
- Retrieving customers filtered by business name or email for targeted marketing.
- Getting a limited number of customers sorted by first name or city for display in a dashboard.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all matching customer records or limit the number of results returned. |
| Limit | The maximum number of customer records to return when "Return All" is false. Minimum value is 1. |
| Filters | Collection of filters to narrow down the customer search: |
| - Business Name | Filter customers by their business name (string). |
| Filter customers by email address (string). | |
| - First Name | Filter customers by first name (string). |
| - Include Disabled | Whether to include disabled customers in the results (boolean). |
| - Last Name | Filter customers by last name (string). |
| - Search Query | A general search query string that can match any customer-related data like name, etc. |
| - Sort | Specify sorting order by customer fields, e.g., "firstname ASC", "city DESC". |
Output
The node outputs an array of customer objects in the json output field. Each object represents a customer record retrieved from Syncro RMM and includes customer details such as names, emails, business names, status, and other relevant fields as provided by the API.
If binary data were involved, it would be summarized here, but this node focuses on JSON customer data only.
Dependencies
- Requires an active connection to the Syncro RMM API.
- Needs an API key credential configured in n8n with appropriate permissions to access customer data.
- The base URL for API requests is dynamically constructed using the user's Syncro RMM subdomain.
- Content-Type and Accept headers are set to handle JSON data.
Troubleshooting
- Invalid API Key: If the API key is incorrect or expired, the node will fail authentication. Error message: "The API Key included in the request is invalid." Solution: Verify and update the API key credential.
- No Results Returned: If filters are too restrictive or no customers match the criteria, the output will be empty. Try broadening filters or removing them.
- Limit Misconfiguration: Setting the limit below 1 may cause errors. Ensure the limit is at least 1 when not returning all.
- API Connectivity Issues: Network problems or incorrect subdomain configuration can cause failures. Check network connectivity and subdomain correctness.
Links and References
- Syncro RMM API Documentation (for detailed API endpoints and data structures)
- n8n documentation on Creating Custom Nodes
