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
This node interacts with the Close.com CRM platform, specifically to retrieve multiple activity records of various types such as calls, emails, meetings, notes, and SMS. The "Get Many" operation under the "Activity" resource allows users to fetch a list of activities filtered by type and other optional criteria.
Typical use cases include:
- Extracting recent communication activities related to leads or contacts for reporting or analysis.
- Synchronizing activity data from Close.com into another system or database.
- Monitoring user or team engagement by retrieving activities performed within a specific timeframe.
For example, a sales automation workflow might use this node to pull all email activities associated with a particular lead ID created in the last month.
Properties
| Name | Meaning |
|---|---|
| Activity Type | The type of activity to retrieve. Options: Call, Email, Meeting, Note, SMS, or All (all types). |
| Return All | Whether to return all matching results or limit the number of returned items. |
| Limit | Maximum number of results to return if not returning all. Minimum is 1. |
| Filter Options | Additional filters to narrow down results: |
| - Lead ID | Filter activities by a specific lead's ID. |
| - Contact ID | Filter activities by a specific contact's ID. |
| - User ID | Filter activities by a specific user's ID. |
| - Date From | Only include activities created after this date/time. |
| - Date To | Only include activities created before this date/time. |
Output
The node outputs an array of JSON objects representing the retrieved activities. Each object corresponds to one activity record and includes fields relevant to the activity type, such as timestamps, associated lead/contact/user IDs, content details, and metadata.
If binary data were involved (e.g., attachments), it would be included in a separate binary property, but this node focuses on JSON data output only.
Dependencies
- Requires an API key credential for authenticating with the Close.com CRM API.
- The node depends on the Close.com REST API endpoints to fetch activity data.
- No additional external services are required beyond the Close.com API access.
Troubleshooting
Common Issues:
- Incorrect or missing API credentials will cause authentication failures.
- Specifying invalid or non-existent lead/contact/user IDs in filters may result in empty responses.
- Requesting too many records without enabling "Return All" can truncate results unexpectedly.
Error Messages:
"The resource "activity" is not known!"— This indicates a misconfiguration of the resource parameter; ensure "Activity" is selected.- API errors from Close.com (e.g., rate limits, invalid parameters) will be surfaced as error messages in the node output or cause execution failure unless "Continue On Fail" is enabled.
Resolutions:
- Verify API credentials and permissions.
- Double-check filter values for correctness.
- Use "Return All" cautiously to avoid large data loads that may impact performance.