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
Meeting → Search Meetings
AI-generatedOverview
The node named "Surense" provides integration with the Surense API, allowing users to interact with various resources such as Meetings, Customers, Contacts, Leads, and more. Specifically for the Meeting resource and the Search Meetings operation, this node enables searching for meetings based on criteria like sorting order, sorting field, pagination, and quick search filters.
This node is beneficial in scenarios where you want to programmatically retrieve meeting data from Surense, for example:
- Fetching a list of recent meetings sorted by creation date.
- Searching meetings with specific keywords or identifiers.
- Paginating through large sets of meeting records efficiently.
Practical examples include automating reporting workflows, syncing meeting data with other systems, or filtering meetings for follow-up actions.
Properties
| Name | Meaning |
|---|---|
| Order | Sort order of the results: ascending (asc) or descending (desc). |
| Order By | Field to sort the results by: creation date (createdDate) or last activity date (lastActivityDate). |
| Limit | Maximum number of meeting results to return (minimum 1). |
| Page | Page number for paginated results (minimum 1). |
| Additional Parameters | Collection of extra parameters; currently supports a "Quick Filter" string to search by name, ID, email, or phone. |
Output
The output of the node is an array of JSON objects representing the meetings retrieved from the Surense API according to the specified search criteria. Each item in the output corresponds to one meeting record with its associated fields as returned by the API.
If any error occurs during execution for a particular input item and the node is configured to continue on failure, the output will contain an object with an error field describing the issue.
The node does not explicitly handle binary data output.
Dependencies
- Requires an active connection to the Surense API via an OAuth2 API credential.
- The node depends on the Surense API being accessible and properly authenticated.
- Pagination and sorting are handled internally but rely on the API's support for these features.
Troubleshooting
- Common issues:
- Authentication failures due to invalid or expired API credentials.
- API rate limits or connectivity problems causing request failures.
- Invalid parameter values such as negative page numbers or limits outside allowed ranges.
- Error messages:
- Errors returned from the Surense API will be surfaced in the node output if "Continue On Fail" is enabled.
- Typical errors might include "Unauthorized", "Invalid parameter", or "Resource not found".
- Resolutions:
- Verify and refresh API credentials.
- Ensure all required parameters are correctly set and within valid ranges.
- Check network connectivity and API status.
Links and References
- Surense API Documentation (replace with actual URL)
- n8n documentation on Creating Custom Nodes
- OAuth2 authentication setup guides in n8n
Note: This summary is based solely on static analysis of the provided source code and property definitions.