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 integrates with Close.com CRM to retrieve detailed information about activities such as calls, emails, meetings, notes, and SMS messages. Specifically, the "Activity - Get" operation fetches a single activity record by its ID, optionally filtered or enriched with additional parameters.
Use cases include:
- Fetching details of a specific phone call or email logged in Close.com.
- Retrieving meeting notes or SMS activity for follow-up or reporting.
- Integrating activity data into workflows for customer engagement tracking.
For example, you might use this node to get the details of a particular email activity associated with a contact to trigger further automation based on that interaction.
Properties
| Name | Meaning |
|---|---|
| Activity Type | The type of activity to retrieve. Options: Call, Email, Meeting, Note, SMS, or All (for getAll). |
| Activity ID | The unique identifier of the activity to fetch. |
| Additional Fields | Optional extra parameters to refine the request: - Contact ID: ID of the related contact. - User: The user who performed the activity. - Date Created: Custom creation date for the activity. - Fields: Comma-separated list of fields to include in the response. |
Output
The node outputs JSON data representing the requested activity's details. This includes all standard fields relevant to the activity type (call, email, meeting, note, or SMS) and any additional fields specified.
If binary data were involved (e.g., attachments), it would be included in a binary property, but this node primarily returns structured JSON data about the activity.
Dependencies
- Requires an API key credential for Close.com CRM configured in n8n.
- Relies on Close.com's REST API endpoints to fetch activity data.
- No other external dependencies are needed.
Troubleshooting
Common issues:
- Invalid or missing Activity ID will cause errors; ensure the ID is correct and exists in Close.com.
- Incorrect Activity Type selection may result in no data or errors if the ID does not match the type.
- Network or authentication failures can occur if the API key is invalid or expired.
Error messages:
"The resource "activity" is not known!"indicates a misconfiguration in the resource parameter.- API errors from Close.com (e.g., 404 Not Found) usually mean the activity ID does not exist.
Resolutions:
- Double-check the Activity ID and Activity Type inputs.
- Verify the API key credential is valid and has sufficient permissions.
- Use the "Additional Fields" to narrow down or enrich the query if needed.