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, specifically providing operations on various CRM resources including custom fields. The "Get Schema" operation for the "Custom Field" resource retrieves the schema or metadata describing the structure and properties of custom fields associated with a specified object type in Close.com.
Typical use cases include:
- Dynamically fetching the schema of custom fields to understand what data can be stored or retrieved for leads, contacts, opportunities, activities, or custom objects.
- Automating workflows that depend on the structure of custom fields, such as form generation, validation, or data mapping.
- Synchronizing custom field definitions between Close.com and other systems.
For example, a user might want to get the schema of custom fields for "Lead" objects to build a dynamic UI that allows users to input lead-specific custom data.
Properties
| Name | Meaning |
|---|---|
| Object Type | The type of object this custom field applies to. Options: Lead, Contact, Opportunity, Activity, Custom Object |
Output
The node outputs JSON data representing the schema of the custom fields for the selected object type. This typically includes details such as field names, types, labels, and possibly other metadata describing each custom field available for that object type.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for Close.com to authenticate requests.
- The node depends on the Close.com API endpoints to fetch custom field schemas.
- No additional external services are required beyond Close.com.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Selecting an unsupported or incorrect object type may result in empty or error responses.
- Network connectivity issues can prevent successful API calls.
Error messages:
"The resource \"customField\" is not known!"— indicates an invalid resource parameter; ensure "Custom Field" is selected.- API errors from Close.com (e.g., 401 Unauthorized) suggest checking the API key validity and permissions.
Resolutions:
- Verify that the API key credential is correctly configured and has sufficient permissions.
- Confirm the object type selection matches one of the supported options.
- Check network connectivity and proxy settings if applicable.