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 with the Get operation, it retrieves detailed information about a specific task by its ID. This is useful when you want to fetch up-to-date details of a task within your workflow, such as checking its status, description, or other metadata.
Practical examples include:
- Fetching a task's details before updating or completing it.
- Retrieving task information to display in reports or dashboards.
- Using task data to trigger conditional logic in automation workflows.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique identifier of the task to retrieve. |
| Additional Fields | Optional extra parameters to customize the response. Currently supports: |
| Fields | Comma-separated list of specific fields to include in the response (e.g., "status,due_date"). |
Output
The node outputs JSON data representing the requested task's details as returned by the Close.com API. The structure typically includes all standard task properties such as ID, name, status, due date, assigned user, and any other fields specified via the "Fields" additional parameter.
If binary data were involved (not indicated here), it would be summarized accordingly, but this node focuses on JSON task data only.
Dependencies
- Requires an active connection to Close.com CRM via an API key credential configured in n8n.
- The node depends on the Close.com REST API to fetch task data.
- No additional external services are required beyond the Close.com API.
Troubleshooting
Common issues:
- Invalid or missing Task ID will cause the API call to fail.
- Insufficient permissions or invalid API credentials can result in authentication errors.
- Specifying invalid field names in the "Fields" parameter may lead to incomplete or error responses.
Error messages:
"The resource "task" is not known!"— indicates a misconfiguration of the resource parameter.- API errors from Close.com (e.g., 404 Not Found if the task ID does not exist).
Resolutions:
- Ensure the Task ID is correct and exists in Close.com.
- Verify that the API key credential has sufficient permissions.
- Use valid field names as per Close.com API documentation when specifying additional fields.