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 Close.com CRM to manage custom fields on various object types such as leads, contacts, opportunities, activities, and custom objects. Specifically, the Create operation for the Custom Field resource allows users to define new custom fields within their Close.com account.
Use cases include:
- Adding tailored data fields to CRM objects to capture information specific to your business needs.
- Creating choice fields with predefined options for consistent data entry.
- Defining required fields to enforce data completeness.
- Supporting multiple values in a single field when needed.
For example, you might create a custom "Customer Priority" choice field on leads with options like "High", "Medium", and "Low", or a "Contract Expiry Date" date field on opportunities.
Properties
| Name | Meaning |
|---|---|
| Object Type | The type of object this custom field applies to. Options: Lead, Contact, Opportunity, Activity, Custom Object. |
| Field Type | The type of the custom field. Options: Text, Number, Date, DateTime, Choice, Boolean. |
| Name | The name of the custom field. |
| Additional Fields | Optional additional settings for the custom field: |
| - Description | A textual description of the custom field. |
| - Is Required | Whether this field is mandatory to fill. (true/false) |
| - Accepts Multiple Values | Whether the field can hold multiple values. (true/false) |
| - Choices | Comma-separated list of choices (only applicable if Field Type is Choice). |
Output
The node outputs JSON data representing the result of the custom field creation request. This typically includes details about the newly created custom field such as its ID, name, type, and other metadata returned by the Close.com API.
No binary data output is involved.
Dependencies
- Requires an active connection to Close.com CRM via an API key credential configured in n8n.
- The node uses Close.com's REST API endpoints to perform actions.
- No additional external dependencies beyond the Close.com API and n8n's HTTP client are required.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing invalid field types or unsupported object types may result in errors from the API.
- Omitting required properties like "Name" or "Object Type" will cause validation errors.
- For choice fields, failing to provide choices or providing them incorrectly (e.g., empty string) may cause errors.
Error messages:
"The resource \"customField\" is not known!"— indicates an invalid resource parameter; ensure "Custom Field" is selected.- API error responses will be passed through; check the message for details such as "field already exists" or "invalid field type".
Resolution tips:
- Double-check all required parameters are set correctly.
- Ensure the API key has sufficient permissions to create custom fields.
- Validate that choice lists are comma-separated without trailing commas.
- Use the node's "Continue On Fail" option to handle errors gracefully during batch operations.