Close icon

Close

Interact with Close.com CRM

Actions79

Overview

This node integrates with the Close.com CRM platform to retrieve multiple tasks based on specified filters and limits. It is designed to fetch a list of tasks, optionally filtered by various criteria such as assigned user, completion status, due dates, and task type. This operation is useful for automating workflows that require bulk access to task data from Close.com, such as syncing tasks with other systems, generating reports, or triggering actions based on task attributes.

Practical examples include:

  • Retrieving all incomplete tasks assigned to a specific user to send reminders.
  • Fetching tasks due within a certain date range for workload planning.
  • Getting a limited number of tasks filtered by lead ID to analyze customer interactions.

Properties

Name Meaning
Return All Whether to return all matching tasks or limit the number of results returned.
Limit Maximum number of tasks to return when "Return All" is false (minimum 1, default 50).
Filter Options Collection of optional filters to narrow down the tasks retrieved:
  Lead ID Filter tasks by the associated lead's ID.
  Assigned To Filter tasks by the assigned user (selectable from available users).
  Is Complete Filter tasks by their completion status (true or false).
  Task Type Filter tasks by their type (string value).
  Due Date From Filter tasks due after this date/time.
  Due Date To Filter tasks due before this date/time.
  Fields Comma-separated list of specific fields to include in the response for each task.

Output

The node outputs an array of JSON objects representing the tasks retrieved from Close.com. Each object contains task properties according to the requested fields or the default set provided by the API. The structure typically includes identifiers, assignment details, status flags, due dates, and other task metadata.

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 via an API key credential configured in n8n.
  • The node uses Close.com's REST API endpoints to fetch task data.
  • The "Assigned To" filter dynamically loads user options from Close.com, requiring appropriate permissions.

Troubleshooting

  • Common Issues:

    • Incorrect or missing API credentials will cause authentication failures.
    • Using invalid filter values (e.g., non-existent user IDs) may result in empty responses or errors.
    • Requesting too many records without enabling "Return All" can truncate results unexpectedly.

  • Error Messages:

    • "The resource "task" is not known!" — indicates a misconfiguration of the resource parameter; ensure "Task" is selected.
    • API rate limits or network issues may cause request failures; verify connectivity and API usage quotas.
    • Validation errors on input parameters (e.g., invalid date formats) should be corrected per the property definitions.

Links and References

Discussion