Actions83
- Lead Actions
- Lead Status Actions
- Contact Actions
- Opportunity Actions
- Opportunity Status Actions
- Task Actions
- Note Actions
- Call Actions
- Email Actions
- Meeting Actions
- SMS Actions
- Custom Activity Actions
- Sequence (Automation & Bulk Actions) Actions
- Bulk Action (Automation & Bulk Actions) Actions
- Export (Automation & Bulk Actions) Actions
- Field Enrichment (Automation & Bulk Actions) Actions
Meeting → Find
AI-generatedOverview
This node operation finds meetings in the Close CRM system based on specified filters. It allows users to retrieve meetings filtered by lead ID, user ID, and additional date-related filters such as creation date and activity date. Users can choose to return all matching meetings or limit the number of results. This operation is useful for scenarios where you need to query and analyze meeting data related to specific leads or users, for example, to track meeting history or follow up on recent activities.
Use Case Examples
- Find all meetings associated with a specific lead ID to review past interactions.
- Retrieve meetings for a particular user within a date range to analyze user activity.
- Get a limited number of recent meetings filtered by creation date for reporting purposes.
Properties
| Name | Meaning |
|---|---|
| Lead ID | Filter meetings by lead ID to find meetings related to a specific lead. |
| User ID | Filter meetings by user ID to find meetings associated with a particular user. |
| Additional Filters | Additional date-based filters to narrow down meetings by creation date or activity date. |
| Return All | Whether to return all matching meetings or limit the results. |
| Limit | Maximum number of meeting results to return when not returning all. |
Output
JSON
id- Unique identifier of the meeting.lead_id- ID of the lead associated with the meeting.user_id- ID of the user associated with the meeting.activity_at- Timestamp of the meeting activity.date_created- Timestamp when the meeting was created.user_note_html- User notes in HTML format related to the meeting.outcome_id- Identifier for the outcome of the meeting.
Dependencies
- Close CRM API
- an API key credential for authentication
Troubleshooting
- Ensure that the Meeting ID is provided when using get, update, or delete operations to avoid errors.
- Check date filter formats to be valid ISO date strings to prevent request failures.
- If no meetings are returned, verify that the filters (lead ID, user ID, date ranges) are correctly set and that matching meetings exist in the CRM.
- API rate limits or authentication issues may cause request failures; verify API credentials and usage limits.
Links
- Close CRM API - Meeting Activity - Official API documentation for managing meeting activities in Close CRM.