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, specifically allowing users to update contact records. It is useful in scenarios where you need to programmatically modify existing contact information such as names, job titles, email addresses, or phone numbers within your CRM system. For example, you might use this node to update a contact's email address after receiving new information from a lead generation form or to correct a phone number.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique identifier of the contact to update. |
| Update Fields | A collection of fields to update on the contact: |
| - Name | The contact's full name. |
| - Title | The job title of the contact. |
| - Email Addresses | One or more email addresses for the contact. Each email has: |
| Type | Type of email address: Office, Personal, or Other. |
| The actual email address string. | |
| - Phone Numbers | One or more phone numbers for the contact. Each phone number has: |
| Type | Type of phone number: Office, Mobile, Home, or Other. |
| Phone | The actual phone number string. |
Output
The node outputs JSON data representing the updated contact record(s) as returned by the Close.com API. This typically includes the contact's ID, updated fields, and metadata confirming the successful update. The output does not include binary data.
Dependencies
- Requires an API key credential for authenticating with the Close.com API.
- The node depends on the Close.com HTTP API endpoints for contacts.
- Proper configuration of the API key credential in n8n is necessary for operation.
Troubleshooting
Common Issues:
- Invalid or missing Contact ID will cause the update to fail.
- Providing no fields to update (empty updateFields) may result in no changes or errors.
- Incorrectly formatted email or phone entries could be rejected by the API.
- Network or authentication errors if the API key is invalid or expired.
Error Messages:
"The resource "contact" is not known!"— indicates an unsupported resource was selected; ensure "Contact" is chosen.- API errors related to invalid input will usually return descriptive messages from Close.com; verify all required fields are correctly set.
- If the node throws an error about credentials, check that the API key is configured and valid.
Resolution Tips:
- Double-check the Contact ID exists in your Close.com account.
- Ensure at least one field is provided in "Update Fields".
- Validate email and phone formats before running the node.
- Confirm API key permissions and validity.