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 interact with various CRM resources programmatically. Specifically, for the User resource with the Get Many operation, it retrieves multiple user records from Close.com.
Typical use cases include:
- Synchronizing user data from Close.com into other systems.
- Automating workflows that require bulk user information.
- Reporting or analytics tasks where user details are needed in volume.
For example, a marketing automation workflow might fetch all users to assign leads or tasks based on user roles or availability.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all user records or limit the number of results returned. |
| Limit | Maximum number of user records to return (only applicable if "Return All" is false). |
| Additional Fields | Optional extra fields to include in the response, specified as a comma-separated string. |
The Additional Fields property allows specifying which user fields to include in the API response, enabling tailored data retrieval.
Output
The node outputs an array of JSON objects representing user records retrieved from Close.com. Each object contains user properties such as name, email, and any additional requested fields.
If binary data were involved (not applicable here), it would be summarized accordingly, but this node deals solely with JSON user data.
Dependencies
- Requires an API key credential for authenticating with Close.com.
- The node depends on the Close.com REST API endpoints for user data.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
Common Issues:
- Authentication failures due to invalid or missing API keys.
- Exceeding API rate limits imposed by Close.com.
- Requesting fields that do not exist or are misspelled in the "Additional Fields" property.
Error Messages:
"The resource "user" is not known!"— indicates an invalid resource parameter; ensure "User" is selected.- Network or HTTP errors from the Close.com API will propagate; verify network connectivity and API status.
- If the node returns an error object in output JSON, check the error message for details.
Resolutions:
- Verify and update the API key credential.
- Adjust request limits or enable "Return All" carefully to avoid large payloads.
- Double-check field names in "Additional Fields" against Close.com API documentation.
Links and References
- Close.com API Documentation
- n8n Documentation on Credentials
- Close.com User Resource API Reference (for detailed field info)