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 → Search Customers
AI-generatedOverview
The node named "Surense" provides integration with the Surense API, allowing users to interact with various resources such as Customers, Contacts, Leads, Meetings, and more. Specifically, for the Customer resource and the Search Customers operation, this node enables searching for customers in the Surense system based on sorting, pagination, and quick filter criteria.
This node is beneficial when you want to automate workflows that require retrieving customer data from Surense, such as syncing customer lists, filtering customers by recent activity or creation date, or implementing custom search queries within your automation.
Practical example:
You could use this node to fetch the top 50 most recently updated customers sorted in descending order, optionally filtered by a search term like a name or email, and then process or export this data further in your workflow.
Properties
| Name | Meaning |
|---|---|
| Order | Sort order of results: ascending (asc) or descending (desc). |
| Order By | Field to sort by: creation date (createdDate) or last activity date (lastActivityDate). |
| Limit | Maximum number of results to return (minimum 1). |
| Page | Page number for pagination (minimum 1). |
| Additional Parameters | Collection of extra parameters; currently supports: |
| - Quick Filter | A quick search string to filter customers by name, ID, email, or phone number. |
Output
The node outputs an array of JSON objects representing the customers matching the search criteria. Each item in the output corresponds to one customer record retrieved from the Surense API.
- The
jsonfield contains the customer data fields returned by the API. - If an error occurs during execution and "Continue On Fail" is enabled, the output will include an object with an
errormessage describing the failure.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Surense API via OAuth2 authentication.
- The node depends on proper configuration of the Surense OAuth2 API credentials within n8n.
- Pagination and sorting are handled internally but rely on the Surense API's support for these features.
Troubleshooting
Common issues:
- Invalid or expired API credentials will cause authentication failures.
- Providing invalid values for pagination (e.g., page < 1) or limit may result in errors.
- Using unsupported sort fields or orders might lead to unexpected results or API errors.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Errors returned from the Surense API will be surfaced in the node output if "Continue On Fail" is enabled.
- Typical error messages might include authentication failures, invalid parameter errors, or rate limiting notices.
Resolutions:
- Verify and refresh API credentials if authentication fails.
- Ensure input parameters conform to expected types and ranges.
- Check network connectivity and API service status.
- Use the "Quick Filter" parameter carefully to avoid malformed queries.
Links and References
- Surense API Documentation (hypothetical link, replace with actual if available)
- n8n OAuth2 Credential Setup Guide: https://docs.n8n.io/credentials/oauth2/
- n8n Pagination Concepts: https://docs.n8n.io/nodes/advanced/pagination/
Note: This summary is based solely on static analysis of the provided source code and property definitions without runtime execution or external API inspection.