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 CRM resources. Specifically, for the Lead - Update operation, it updates an existing lead's details in Close.com. This is useful when you want to modify lead information such as name, description, status, website URL, addresses, or custom fields programmatically within an n8n workflow.
Practical examples include:
- Automatically updating lead statuses based on external triggers.
- Enriching lead data with additional information from other systems.
- Correcting or appending address and contact details for leads in bulk.
Properties
| Name | Meaning |
|---|---|
| Lead ID | The unique identifier of the lead to update. |
| Update Fields | A collection of fields to update on the lead, including: |
| Name | The name of the lead or company. |
| Description | A textual description of the lead. |
| Status | The status ID representing the lead's current state. Options are dynamically loaded from Close.com lead statuses. |
| URL | The website URL associated with the lead. |
| Custom Fields | Custom fields (non-user type) to update on the lead. Multiple can be specified, each with a field and value. |
| User Custom Fields | User-type custom fields to update, where each field is assigned a user selected from available users. |
| Addresses | Addresses to update for the lead. Multiple addresses can be added, each with: |
| Type | Type of address: Office, Mailing, or Other. |
| Address Line 1 | First line of the address. |
| Address Line 2 | Second line of the address (optional). |
| City | City name. |
| State | State or province. |
| Postal Code | Postal or ZIP code. |
| Country | Country name. |
Output
The node outputs JSON data representing the updated lead object as returned by the Close.com API. This typically includes all lead properties after the update, such as IDs, names, statuses, URLs, addresses, and any custom fields.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to Close.com via an API key credential configured in n8n.
- The node uses Close.com's REST API endpoints to fetch dynamic options (e.g., lead statuses, custom fields, users) and to perform the update action.
- Network connectivity to Close.com's API is necessary.
Troubleshooting
Common issues:
- Invalid or missing Lead ID: The update will fail if the provided Lead ID does not exist or is malformed.
- Insufficient permissions: The API key used must have rights to update leads.
- Invalid field values: Providing invalid status IDs or custom field values may cause errors.
- Network or authentication errors connecting to Close.com.
Error messages:
"The resource "lead" is not known!"— indicates an unsupported resource was selected; ensure "Lead" is chosen.- API errors from Close.com will be passed through; check the error message for details like invalid IDs or permission issues.
Resolution tips:
- Verify the Lead ID exists in Close.com before attempting update.
- Confirm API credentials are valid and have appropriate scopes.
- Use the dynamic dropdowns for statuses, custom fields, and users to avoid invalid values.
- Enable "Continue On Fail" in the node settings to handle partial failures gracefully.
Links and References
- Close.com API Documentation
- Close.com Lead Resource API
- n8n Documentation on Creating Custom Nodes