Actions79
- Lead Status Actions
- Pipeline Actions
- Template Actions
- Lead Actions
- Contact Actions
- Activity Actions
- Meeting Search Actions
- Opportunity Actions
- Opportunity Status Actions
- Integration Link Actions
- Smart View Actions
- Comment Actions
- Email Template Actions
- Task Actions
- User Actions
- Custom Field Actions
Overview
The "Meeting Search" resource with the "Search" operation allows users to query and retrieve meetings from a CRM system based on various filtering criteria. This node is useful for scenarios where you want to find specific meetings by attributes such as date range, associated user, lead, or contact, or by custom search queries. For example, you could use it to fetch all meetings related to a particular sales lead within the last month or to get meetings involving a specific user.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all matching meeting results or limit the output to a specified number of items. |
| Limit | The maximum number of meeting results to return when not returning all. |
| Search Options | A collection of optional filters to refine the search: |
| - Query | JSON-formatted search query to filter meetings by fields like title or date (e.g., {"title": "standup"}). |
| - User ID | Filter meetings associated with a specific user by their ID. |
| - Lead ID | Filter meetings linked to a particular lead by its ID. |
| - Contact ID | Filter meetings linked to a particular contact by its ID. |
| - Date From | Filter meetings starting from this date/time (inclusive). |
| - Date To | Filter meetings up to this date/time (inclusive). |
| - Fields | Comma-separated list of specific fields to include in the response for each meeting. |
Output
The node outputs an array of JSON objects representing meetings that match the search criteria. Each object contains meeting details according to the requested fields or default fields if none are specified. The structure typically includes properties such as meeting title, date/time, participants, and related entities (user, lead, contact).
If binary data were involved (e.g., attachments), it would be included in the binary property of the output items, but this node focuses on JSON meeting data only.
Dependencies
- Requires an API key credential for authenticating with the Close.com CRM API.
- The node depends on the Close.com API endpoints for searching meetings.
- Proper configuration of the API authentication credential in n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication errors.
- Malformed JSON in the "Query" field can cause parsing errors or failed requests.
- Requesting too many results without enabling "Return All" may result in truncated data.
- Filtering by IDs (User, Lead, Contact) that do not exist or are incorrect will yield empty results.
Error messages:
"The resource "meetingSearch" is not known!"— indicates an invalid resource selection; ensure "Meeting Search" is selected.- API errors related to rate limits or permissions should be resolved by checking API key scopes and usage.
- JSON parsing errors for the "Query" parameter require validating the JSON syntax before input.
Links and References
- Close.com API Documentation
- n8n Documentation on Credentials
- JSON validation tools (e.g., https://jsonlint.com/) for verifying the "Query" input format