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 the Close.com CRM platform, allowing users to perform various operations on different CRM resources. Specifically, for the Activity resource with the Delete operation, it enables users to delete an activity record such as a call, email, meeting, note, or SMS from their Close.com account.
This is useful in scenarios where you want to automate cleanup of outdated or incorrect activities, maintain data hygiene, or integrate deletion workflows triggered by external events. For example, if a meeting was canceled and logged incorrectly, this node can be used to remove that meeting activity automatically.
Properties
| Name | Meaning |
|---|---|
| Activity Type | The type of activity to delete. Options: Call, Email, Meeting, Note, SMS |
| Activity ID | The unique identifier of the activity to delete |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will confirm whether the deletion was successful or provide error details if it failed.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Close.com API.
- The node depends on the Close.com REST API endpoints for managing activities.
- Proper network access to Close.com's API endpoints is necessary.
Troubleshooting
Common issues:
- Invalid or missing Activity ID: The node requires a valid activity ID; ensure the ID exists and is correct.
- Insufficient permissions: The API key must have rights to delete activities.
- Network or authentication errors: Check API credentials and network connectivity.
Error messages:
"The resource "activity" is not known!"— This indicates an invalid resource parameter; ensure "Activity" is selected.- API errors returned from Close.com (e.g., 404 Not Found) usually mean the activity ID does not exist or has already been deleted.
Resolution tips:
- Verify the activity ID before running the node.
- Confirm API credentials are valid and have delete permissions.
- Use the node's "Continue On Fail" option to handle errors gracefully in workflows.