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 perform various operations on CRM resources. Specifically, for the Contact - Create operation, it allows users to create a new contact associated with a lead in Close.com. This is useful when you want to programmatically add contacts related to sales leads, such as adding a new decision-maker or point of contact for a potential deal.
Practical examples:
- Automatically creating a contact when a new lead is generated from a web form.
- Adding multiple contacts to a lead during a data migration or synchronization process.
- Enriching lead information by associating detailed contact info like emails and phone numbers.
Properties
| Name | Meaning |
|---|---|
| Lead ID | The unique identifier of the lead this contact belongs to (required). |
| Name | The full name of the contact. |
| Title | The job title or position of the contact within their organization. |
| Additional Fields | A collection of optional fields to provide more contact details: |
| - Email Addresses | Multiple email addresses for the contact, each with a type: Office, Personal, or Other. |
| - Phone Numbers | Multiple phone numbers for the contact, each with a type: Office, Mobile, Home, or Other. |
Output
The node outputs JSON data representing the created contact object returned by the Close.com API. This typically includes the contact's ID, associated lead ID, name, title, emails, phones, and any other metadata provided or generated by the API.
If the node supports binary data output (not indicated here), it would represent attachments or files related to the contact, but this node focuses on JSON data only.
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 request capabilities.
Troubleshooting
Common issues:
- Invalid or missing Lead ID: The contact must be linked to an existing lead; ensure the Lead ID is correct.
- API authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Network or connectivity problems: Ensure n8n can reach Close.com's API endpoints.
Error messages:
"The resource "contact" is not known!"— This indicates an invalid resource parameter; verify the resource selection.- API errors returned from Close.com will be passed through; check the error message for details such as validation failures or rate limits.
Resolution tips:
- Double-check all required fields are provided.
- Use the "Continue On Fail" option in n8n to handle individual item errors gracefully.
- Review API credentials and permissions if authentication fails.