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 Complete operation, the node marks a specified task as completed within Close.com. This is useful in workflows where task management is automated, such as closing tasks after certain conditions are met or syncing task statuses between systems.
Practical examples:
- Automatically completing a sales follow-up task once an email has been sent.
- Marking support tickets' related tasks as done when the ticket is resolved.
- Closing reminder tasks after a meeting has been logged.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique identifier of the task to complete. |
Output
The node outputs JSON data representing the result of the "complete task" operation from Close.com. This typically includes details about the updated task, confirming its completion status and any other relevant metadata returned by the API.
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 Complete operation on tasks.
Dependencies
- Requires an API key credential for Close.com to authenticate requests.
- Depends on the Close.com REST API endpoint for tasks.
- The node uses internal HTTP client utilities to communicate with Close.com.
Troubleshooting
Common issues:
- Invalid or missing Task ID: The operation will fail if the provided Task ID does not exist or is malformed.
- Authentication errors: If the API key is invalid or missing, the node will throw authentication errors.
- Network or API downtime: Temporary failures may occur if Close.com's API is unreachable.
Error messages:
"The resource "task" is not known!"— indicates an unsupported resource was selected; ensure "Task" is chosen.- Errors containing
"error"in the output JSON indicate specific API or validation failures; check the message for details.
Resolutions:
- Verify the Task ID is correct and corresponds to an existing task.
- Ensure the API key credential is properly configured and has necessary permissions.
- Use the node's "Continue On Fail" option to handle errors gracefully in workflows.