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 Close.com CRM to perform various operations on different resources. Specifically, for the Task resource with the Create operation, it allows users to create new tasks associated with leads in their Close.com account. This is useful for automating task creation workflows such as assigning follow-up actions, scheduling reminders, or tracking activities related to sales leads.
Practical examples include:
- Automatically creating a task to call a lead after a form submission.
- Assigning a task to a specific user to prepare a proposal by a certain due date.
- Marking tasks as complete programmatically based on other workflow triggers.
Properties
| Name | Meaning |
|---|---|
| Lead ID | The unique identifier of the lead to which this task belongs. |
| Text | The description or content of the task. |
| Assigned To | The user responsible for completing the task. Options are dynamically loaded from users. |
| Due Date | The deadline or due date/time for the task completion. |
| Is Complete | Boolean flag indicating whether the task is marked as completed. |
| Additional Fields | A collection of optional fields: - Contact ID: ID of the contact linked to the task. - Task Type: The category or type of the task. |
Output
The node outputs JSON data representing the created task object returned from Close.com API. This typically includes all details of the newly created task such as its ID, text, assigned user, due date, status, and any additional metadata.
No binary data output is involved.
Dependencies
- Requires an active connection to Close.com CRM via an API key credential configured in n8n.
- The node uses Close.com REST API endpoints to perform task creation.
- Dynamic loading of users for the "Assigned To" property requires API access to fetch user lists.
Troubleshooting
Common issues:
- Invalid or missing Lead ID will cause task creation to fail.
- Assigning a task to a non-existent user or invalid user ID will result in errors.
- Incorrect date format for Due Date may cause API rejection.
- Insufficient permissions or invalid API credentials will prevent successful API calls.
Error messages:
"The resource "task" is not known!"— indicates a misconfiguration of the resource parameter.- API errors from Close.com (e.g., 400 Bad Request) usually indicate invalid input data; verify required fields and formats.
- Network or authentication errors suggest checking API key validity and connectivity.
Resolutions:
- Ensure all required fields (Lead ID, Text) are provided and valid.
- Use the dynamic dropdown for "Assigned To" to select valid users.
- Confirm API credentials are correctly set up and have necessary scopes.
- Validate date/time inputs conform to expected ISO format.