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 update an existing activity record. Activities in Close.com represent various interactions such as calls, emails, meetings, notes, and SMS messages related to leads or contacts.
The "Update Activity" operation allows users to modify details of a specific activity by its ID. This is useful for keeping activity records accurate and up-to-date, for example:
- Correcting or adding notes to a call or meeting.
- Updating the subject or body of an email activity.
- Changing the duration or direction of a call.
- Adjusting meeting times or location.
- Editing SMS text content.
Practical scenarios include syncing updated communication details from other systems, correcting data entry errors, or enriching activity logs with additional information.
Properties
| Name | Meaning |
|---|---|
| Activity Type | The type of activity to update. Options: Call, Email, Meeting, Note, SMS |
| Activity ID | The unique identifier of the activity to update |
| Update Fields | Collection of fields to update depending on the activity type: |
| - Note | Text note or content of the activity |
| - Duration (Call) | Duration in seconds (only for call activities) |
| - Direction (Call/Email/SMS) | Direction of communication: Inbound or Outbound |
| - Subject (Email) | Subject line of the email activity |
| - Body Text (Email) | Plain text body content of the email |
| - Body HTML (Email) | HTML formatted body content of the email |
| - Title (Meeting) | Title of the meeting |
| - Starts At (Meeting) | Start date and time of the meeting |
| - Ends At (Meeting) | End date and time of the meeting |
| - Location (Meeting) | Location where the meeting takes place |
| - Text (SMS) | Text content of the SMS message |
Output
The node outputs an array of JSON objects representing the updated activity data returned from Close.com after the update operation. Each object contains the updated fields of the activity, reflecting the changes made.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with Close.com CRM.
- The node depends on the Close.com REST API to perform update operations on activities.
- Proper network connectivity to Close.com's API endpoints is necessary.
Troubleshooting
Common Issues:
- Invalid or missing Activity ID will cause the update to fail.
- Providing update fields incompatible with the selected activity type may result in errors.
- Network or authentication failures can prevent successful API calls.
Error Messages:
"The resource "activity" is not known!"— indicates an invalid resource parameter; ensure "Activity" is selected.- API errors from Close.com (e.g., 404 Not Found if activity ID does not exist, 401 Unauthorized if API key is invalid).
Resolutions:
- Verify the Activity ID is correct and exists in Close.com.
- Confirm that the API key credential is valid and has sufficient permissions.
- Match update fields to the correct activity type (e.g., do not set email-specific fields on a call activity).
- Enable "Continue On Fail" in the node settings to handle partial failures gracefully.
Links and References
- Close.com API Documentation - Activities
- Close.com CRM Official Website
- n8n Documentation on Creating Custom Nodes