Close

Interact with Close.com CRM

Actions79

Lead Status Actions
Pipeline Actions
Template Actions
Lead Actions
Contact Actions
Activity Actions
Meeting Search Actions
- Search
Opportunity Actions
Opportunity Status Actions
Integration Link Actions
Smart View Actions
Comment Actions
Email Template Actions
Task Actions
User Actions
- Get
- Get Many
Custom Field Actions

Overview

This node integrates with the Close.com CRM platform, specifically providing operations on various CRM resources. The "Contact" resource with the "Get Many" operation allows users to retrieve multiple contact records from Close.com. This is useful for scenarios where you want to fetch a list of contacts based on certain filters or criteria, such as syncing contacts to another system, generating reports, or performing bulk updates.

For example, you might use this node to:

Retrieve all contacts associated with a specific lead.
Search contacts by name or email using a JSON query.
Limit the number of contacts returned to avoid overwhelming downstream processes.

Properties

Name	Meaning
Return All	Whether to return all matching contacts or limit the results to a specified maximum number.
Limit	Maximum number of contacts to return when "Return All" is false (minimum 1, default 50).
Additional Fields	Collection of optional filters and parameters:
- Lead ID	Filter contacts by a specific lead ID.
- Query	JSON-formatted search query to filter contacts by fields like name or email (e.g., `{"name": "John"}`).
- Fields	Comma-separated list of specific contact fields to include in the response.

Output

The node outputs an array of JSON objects representing the retrieved contacts. Each object contains the contact's data fields as returned by the Close.com API, filtered according to the input properties.

If binary data were supported (not indicated here), it would typically represent attachments or files related to contacts, but this node focuses on JSON data only.

Dependencies

Requires an API key credential for Close.com to authenticate requests.
The node depends on the Close.com REST API endpoints for contacts.
No additional environment variables are explicitly required beyond the API authentication.

Troubleshooting

Common issues:
- Invalid or missing API credentials will cause authentication errors.
- Incorrect JSON format in the "Query" field may result in request failures.
- Requesting too many records without pagination or limits may lead to timeouts or rate limiting.
Error messages:
- "The resource "contact" is not known!" — indicates a misconfiguration of the resource parameter.
- API errors from Close.com (e.g., 400 Bad Request) usually relate to invalid filters or malformed queries; verify JSON syntax and field names.
To resolve errors, ensure correct API credentials, validate JSON inputs, and use the "Limit" property to control data volume.