Close

Interact with Close.com CRM

Actions79

Lead Status Actions
Pipeline Actions
Template Actions
Lead Actions
Contact Actions
Activity Actions
Meeting Search Actions
- Search
Opportunity Actions
Opportunity Status Actions
Integration Link Actions
Smart View Actions
Comment Actions
Email Template Actions
Task Actions
User Actions
- Get
- Get Many
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 Update operation, it enables updating properties of an existing custom field in Close.com.

Typical use cases include:

Modifying the name or description of a custom field to better reflect its purpose.
Changing whether a custom field is required or accepts multiple values.
Updating the list of choices available for choice-type custom fields.

For example, if you have a custom field used to categorize leads and want to add new categories or rename the field, this node operation facilitates that update seamlessly within an automated workflow.

Properties

Name	Meaning
Custom Field ID	The unique identifier of the custom field to update.
Update Fields	A collection of fields to update on the custom field:
- Name	The new name for the custom field.
- Description	A textual description explaining the purpose or details of the custom field.
- Is Required	Boolean flag indicating whether filling out this field is mandatory.
- Accepts Multiple Values	Boolean flag indicating if the field can hold multiple values simultaneously.
- Choices	Comma-separated string listing the selectable options for choice-type custom fields only.

Output

The node outputs an array of JSON objects representing the updated custom field(s). Each output item contains the updated properties as returned by the Close.com API after the update operation.

If the node encounters errors during execution (e.g., invalid field ID), it outputs an error message in the json.error property when "Continue On Fail" is enabled.

No binary data output is produced by this node.

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 updates on custom fields.
No additional external dependencies are needed beyond the configured API authentication.

Troubleshooting

Invalid Custom Field ID: If the provided custom field ID does not exist or is incorrect, the node will throw an error. Verify the ID is correct and corresponds to an existing custom field in your Close.com account.
Insufficient Permissions: Ensure the API key used has permissions to modify custom fields.
Invalid Choices Format: When updating the Choices property, ensure the input is a properly formatted comma-separated string without trailing commas or invalid characters.
API Rate Limits: Frequent updates may hit Close.com's API rate limits; consider adding delays or handling retries.
Error Messages: Errors from the API are surfaced as messages in the node's output under json.error if "Continue On Fail" is enabled. Otherwise, they cause the workflow to stop.