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 Task resource and the Update operation, it enables updating details of an existing task in Close.com. This is useful when you want to programmatically modify task attributes such as description, assignee, due date, completion status, or type.
Common scenarios include:
- Automatically updating task details based on external triggers or workflows.
- Changing task assignments dynamically as team members change.
- Marking tasks complete when certain conditions are met in other systems.
- Adjusting due dates or task types to reflect updated priorities.
Example: You could use this node to update a task's description and mark it as complete once a related sales opportunity is closed.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique identifier of the task to update. |
| Update Fields | A collection of fields to update on the task. Options include: |
| - Text | The description or text content of the task. |
| - Assigned To | The user ID of the person assigned to the task. |
| - Due Date | The due date/time for the task. |
| - Is Complete | Boolean indicating whether the task is marked as complete. |
| - Task Type | The type/category of the task. |
Output
The node outputs JSON data representing the updated task object returned from Close.com after the update operation. This typically includes all task properties reflecting the new state post-update.
If the node supports binary data output (not indicated here), it would represent attachments or files related to the task, but this is not applicable for the update operation on tasks.
Dependencies
- Requires an API key credential for Close.com to authenticate requests.
- The node uses Close.com's REST API endpoints to perform updates.
- No additional environment variables are explicitly required beyond the API authentication.
Troubleshooting
- Invalid Task ID: If the provided Task ID does not exist or is malformed, the API will return an error. Verify the Task ID is correct.
- Permission Errors: Ensure the API key used has sufficient permissions to update tasks.
- Invalid Field Values: Providing invalid values for fields like
dueDate(wrong format) orassignedTo(nonexistent user ID) may cause errors. - Network Issues: Connectivity problems can cause request failures; check network access to Close.com API.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if one update fails, returning error messages in the output JSON.