Close

Overview

This node integrates with the Close.com CRM platform, allowing users to perform various operations on CRM resources such as leads, contacts, activities, opportunities, and more. Specifically, for the Contact resource with the Get operation, the node retrieves detailed information about a specific contact by its unique ID. This is useful in scenarios where you want to fetch up-to-date contact details from your CRM to use in workflows like customer support automation, personalized marketing campaigns, or data synchronization between systems.

For example, you might use this node to:

• Retrieve a contact's full profile before sending a personalized email.
• Fetch contact details to update records in another database.
• Use contact information to trigger conditional logic in an automation workflow.

Properties

Output

The node outputs JSON data representing the contact's details as retrieved from Close.com CRM. The structure typically includes all standard contact fields such as name, email, phone numbers, addresses, and any custom fields associated with the contact.

If the "Fields" option is used, only those specified fields will be included in the output JSON.

No binary data output is indicated for this operation.

Example output snippet (simplified):

{
  "id": "contact_12345",
  "name": "John Doe",
  "emails": [
    {
      "type": "work",
      "email": "john.doe@example.com"
    }
  ],
  "phones": [
    {
      "type": "mobile",
      "phone": "+1234567890"
    }
  ],
  "custom_fields": {
    "field_id_1": "value1",
    "field_id_2": "value2"
  }
}

Dependencies

• Requires an API key credential for Close.com CRM configured in n8n.
• The node uses Close.com's REST API endpoints to perform actions.
• No additional external dependencies are needed beyond the configured API authentication.

Troubleshooting

• Common issues:

  • Invalid or missing Contact ID: The node requires a valid contact ID; ensure it is correctly provided.
  • API authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
  • Network or API downtime: Temporary connectivity issues with Close.com can cause failures.

• Error messages:

  • "The resource \"contact\" is not known!" — This indicates an invalid resource selection; ensure "Contact" is selected.
  • Errors related to missing parameters or invalid IDs will usually mention the parameter name; double-check input values.
  • API rate limits or permission errors will come from the Close.com API; check your account limits and credentials.

To resolve errors, verify inputs, credentials, and network connectivity. Enable "Continue On Fail" in the node settings if you want the workflow to proceed despite individual item errors.

Links and References

• Close.com API Documentation
• Close.com Contacts API Reference
• n8n Documentation on Credentials