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 to create new leads. It allows users to input detailed information about a lead, including its name, description, status, addresses, contacts, and custom fields. This is useful for automating lead generation workflows, syncing data from other systems, or bulk importing leads into Close.com.
Practical examples:
- Automatically creating a lead in Close.com when a form is submitted on a website.
- Importing leads from a spreadsheet or another CRM system.
- Creating leads with associated contacts and addresses for better organization and follow-up.
Properties
| Name | Meaning |
|---|---|
| Name | The name of the lead or company (required). |
| Description | A textual description providing more details about the lead. |
| Status | The current status of the lead. Options are dynamically loaded from Close.com lead statuses. |
| Additional Fields | A collection of optional fields to further describe the lead: |
| - URL | Website URL associated with the lead. |
| - Custom Fields | Custom fields (non-user type) to set on the lead; each requires selecting a field and specifying a value. |
| - User Custom Fields | User-type custom fields to assign specific users to the lead; select a field and assign a user. |
| Addresses | Multiple addresses related to the lead, each with: |
| - Type | Address type: 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. |
| Contacts | Multiple contacts to create along with the lead, each with: |
| - Name | Full name of the contact. |
| - Title | Job title of the contact. |
| - Email Addresses | Multiple email addresses per contact, each with type (Office, Personal, Other) and email string. |
| - Phone Numbers | Multiple phone numbers per contact, each with type (Office, Mobile, Home, Other) and number string. |
Output
The node outputs an array of JSON objects representing the created lead(s) as returned by the Close.com API. Each output item contains the full response data for the created lead, including assigned IDs and any additional metadata provided by the API.
If multiple leads are processed, the output will contain one JSON object per lead.
No binary data output is produced by this node.
Dependencies
- Requires an active Close.com API key credential configured in n8n for authentication.
- Uses Close.com REST API endpoints to perform lead creation and fetch dynamic options such as lead statuses, custom fields, and users.
- Network connectivity to Close.com API is required.
Troubleshooting
- Common issues:
- Invalid or missing API credentials will cause authentication errors.
- Providing invalid field values (e.g., non-existent status ID or custom field ID) may result in API validation errors.
- Network issues can cause request timeouts or failures.
- Error messages:
"The resource "lead" is not known!"— indicates an unsupported resource was selected; ensure "Lead" is chosen.- API error messages from Close.com will be passed through; check the message for details like invalid parameters or permission issues.
- Resolutions:
- Verify API credentials and permissions.
- Use the dynamic dropdowns to select valid statuses, custom fields, and users to avoid invalid IDs.
- Check network connectivity and retry if transient errors occur.
- Enable "Continue On Fail" option in the node settings to handle partial failures gracefully.