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 User - Get operation, it retrieves detailed information about a specific user in the Close.com system by their user ID. This is useful for workflows that need to fetch user details such as name, email, or other profile data for reporting, automation, or synchronization purposes.
Practical examples:
- Fetching user details to assign tasks or activities dynamically based on user attributes.
- Retrieving user information to personalize communications or notifications.
- Synchronizing user data from Close.com into another system or database.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the user to retrieve from Close.com. |
| Additional Fields | Optional collection to specify extra fields to include in the response. |
| Fields | Comma-separated list of additional user fields to include in the API response. |
Output
The node outputs JSON data representing the user object retrieved from Close.com. The structure typically includes standard user properties such as:
id: The user's unique identifier.first_name,last_name: User's name components.email: User's email address.- Other user-specific fields depending on the requested additional fields.
If additional fields are specified, those will be included in the output JSON as well.
The node does not output binary data.
Dependencies
- Requires an active connection to Close.com CRM via an API key credential configured in n8n.
- The node depends on Close.com's REST API endpoints to fetch user data.
- Proper API permissions must be granted to the API key used for authentication.
Troubleshooting
Common issues:
- Invalid or missing User ID: The node requires a valid user ID; otherwise, the API call will fail.
- Insufficient API permissions: The API key must have permission to read user data.
- Network or connectivity problems may cause request failures.
Error messages:
"The resource "user" is not known!"— indicates an invalid resource parameter; ensure "User" is selected.- API errors returned from Close.com (e.g., 404 Not Found if user ID does not exist).
Resolutions:
- Verify the User ID is correct and exists in Close.com.
- Check API key permissions and validity.
- Ensure network connectivity and that Close.com API is reachable.