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 Custom Field resource with the Get operation, it retrieves details of a specific custom field by its ID. This is useful when you want to fetch metadata or configuration about a particular custom field defined in your Close.com account.
Practical scenarios include:
- Fetching custom field definitions to dynamically build forms or UI elements.
- Validating or displaying custom field information before updating or using it elsewhere.
- Integrating Close.com custom field data into other systems or workflows.
Properties
| Name | Meaning |
|---|---|
| Custom Field ID | The unique identifier of the custom field to retrieve. This is required to specify which custom field's details to get. |
Output
The node outputs JSON data representing the details of the requested custom field. The structure typically includes properties such as the field's ID, name, type, and possibly other metadata describing the custom field within Close.com.
If the node supports binary data output (not indicated here), it would represent any associated files or attachments related to the custom field, but this is not applicable for the "Get Custom Field" operation.
Dependencies
- Requires an API key credential for Close.com to authenticate requests.
- The node depends on the Close.com API endpoint
/custom_field/{id}(implied from the context). - No additional external services are needed beyond the Close.com API.
- Proper network access to Close.com's API endpoints is necessary.
Troubleshooting
Common issues:
- Invalid or missing Custom Field ID: The node requires a valid ID; otherwise, the API will return an error.
- Authentication failures: Ensure the API key credential is correctly configured and has sufficient permissions.
- Network connectivity problems can cause request failures.
Error messages:
"The resource "customField" is not known!"— This indicates an invalid resource parameter; ensure "Custom Field" is selected.- API errors returned from Close.com (e.g., 404 Not Found if the custom field ID does not exist).
Resolutions:
- Double-check the Custom Field ID input.
- Verify API credentials and permissions.
- Check network connectivity and API availability.