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 to perform operations on various CRM resources. Specifically, for the Custom Field resource with the Get Many operation, it retrieves multiple custom fields defined in Close.com. This is useful when you want to fetch metadata about custom fields associated with different object types (like leads, contacts, opportunities, or activities) and potentially filter them by field type.
Practical scenarios include:
- Synchronizing custom field definitions from Close.com into another system.
- Dynamically building UI elements based on available custom fields.
- Reporting or auditing custom fields configured in your CRM.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all matching custom fields or limit the number of results returned. |
| Limit | Maximum number of custom fields to return if "Return All" is false. |
| Filter Options | Additional filters to narrow down the custom fields: |
| - Object Type | Filter by the type of object the custom field belongs to. Options: Lead, Contact, Opportunity, Activity. |
| - Field Type | Filter by the type of the custom field. Options: Text, Number, Date, DateTime, Choice, Boolean. |
Output
The node outputs an array of JSON objects representing the custom fields retrieved from Close.com. Each object typically contains details such as the field's ID, name, type, and the object type it belongs to.
If binary data were involved (not applicable here), it would be summarized accordingly, but this node only returns JSON data describing custom fields.
Dependencies
- Requires an API key credential for authenticating with Close.com.
- The node uses Close.com's REST API endpoints to fetch custom field data.
- No additional external dependencies beyond the Close.com API and n8n's HTTP request capabilities.
Troubleshooting
Common Issues:
- Authentication failures due to invalid or missing API credentials.
- Network connectivity issues preventing access to Close.com's API.
- Request limits or pagination not handled properly if "Return All" is false and limit is too low.
Error Messages:
"The resource \"customField\" is not known!"— indicates an unsupported resource was selected; ensure "Custom Field" is chosen.- API errors returned from Close.com will be surfaced; check the error message for details like rate limiting or permission issues.
Resolutions:
- Verify that the API key credential is correctly configured and has sufficient permissions.
- Increase the "Limit" or enable "Return All" to retrieve more results if needed.
- Check network settings and firewall rules to allow outbound requests to Close.com.