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 and the "Delete" operation, it enables users to delete a custom field from their Close.com account by specifying its unique ID.
Common scenarios where this node is beneficial include:
- Automating cleanup of obsolete or unused custom fields in Close.com.
- Managing CRM schema dynamically based on business needs.
- Integrating with workflows that require removing custom fields as part of data lifecycle management.
Practical example:
- A user wants to remove a custom field that is no longer relevant after a product update. By providing the custom field's ID, this node deletes it automatically without manual intervention in the Close.com UI.
Properties
| Name | Meaning |
|---|---|
| Custom Field ID | The unique identifier of the custom field to delete. This is a required string input. |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will confirm the deletion or provide details about the deleted custom field. If an error occurs, the output JSON will contain an error field describing the issue.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Close.com API.
- The node depends on the Close.com HTTP API endpoints for managing custom fields.
- Proper configuration of the API authentication within n8n is necessary for successful execution.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Custom Field ID will cause the operation to fail.
- Missing or incorrect API credentials will prevent the node from connecting to Close.com.
- Network connectivity problems can lead to request timeouts or failures.
Error messages:
"The resource \"customField\" is not known!": Indicates an unsupported resource was selected; ensure "Custom Field" is chosen.- Errors returned from the Close.com API (e.g., 404 Not Found) typically mean the specified custom field ID does not exist.
- Authentication errors suggest invalid or missing API credentials.
Resolutions:
- Verify the Custom Field ID is correct and exists in your Close.com account.
- Check that the API key credential is properly set up and has sufficient permissions.
- Ensure network access to Close.com API endpoints is available.