Actions83
- Lead Actions
- Lead Status Actions
- Contact Actions
- Opportunity Actions
- Opportunity Status Actions
- Task Actions
- Note Actions
- Call Actions
- Email Actions
- Meeting Actions
- SMS Actions
- Custom Activity Actions
- Sequence (Automation & Bulk Actions) Actions
- Bulk Action (Automation & Bulk Actions) Actions
- Export (Automation & Bulk Actions) Actions
- Field Enrichment (Automation & Bulk Actions) Actions
Task → Bulk Update
AI-generatedOverview
This node operation performs a bulk update on tasks within the Close CRM system. It allows users to filter tasks based on criteria such as task IDs, task type, lead ID, completion status, and assigned user ID, and then update multiple fields of those filtered tasks at once. This is useful for scenarios where you need to efficiently update many tasks simultaneously, such as reassigning tasks to a different user, changing their due dates, or updating their completion status.
Use Case Examples
- Bulk update all tasks assigned to a specific user to mark them as complete.
- Change the due date for a set of tasks identified by their IDs.
- Filter tasks by lead ID and update their assigned user.
Properties
| Name | Meaning |
|---|---|
| Filter Tasks | Criteria to filter which tasks will be updated in bulk, including task IDs, task type, lead ID, completion status, and assigned user ID. |
| Update Data | Fields to update on the filtered tasks, such as assigned user, date/time, and completion status. |
Output
JSON
id- The ID of the updated task.assigned_to- The user ID to whom the task is assigned after update.date- The updated date/time of the task.is_complete- The updated completion status of the task.
Dependencies
- Close CRM API access with appropriate credentials
Troubleshooting
- Ensure that at least one update field is provided; otherwise, the node throws an error indicating that update fields are required for bulk update.
- Verify that the filter criteria are correctly specified to target the intended tasks; incorrect filters may result in no tasks being updated.
- Check API credentials and permissions to ensure the node can perform bulk updates on tasks.
- Common error messages include missing required parameters like resource or operation, or invalid JSON in fields if used.