Klipy
Actions13
Overview
This node integrates with the Klipy CRM API to manage company records, specifically allowing you to update existing company information. It is useful in scenarios where you need to keep your CRM data current by modifying details such as company name, domain, description, industry tags, contact info, and social media links.
For example, if a company's address or phone number changes, or if you want to add new tags or remarks about the company, this node can update those fields seamlessly via the API.
Properties
| Name | Meaning |
|---|---|
| Company ID | The unique identifier of the company to update (required). |
| Company Data | The set of fields to update for the company. These include: |
| - Name: The company's name. | |
| - Domain: The company's website domain. | |
| - Description: A textual description of the company. | |
| - Alternative Industries: Comma-separated list of alternative industries related to the company. | |
| - Tags: Comma-separated list of tags associated with the company. | |
| - Founded Year: The year the company was founded. | |
| - Address, City, State, Country: Physical location details. | |
| - Phone: Contact phone number. | |
| - LinkedIn, Twitter, Facebook, Instagram, Crunchbase: Social media and profile URLs. | |
| - Remarks: Additional notes or comments about the company. |
Output
The node outputs JSON data representing the updated company record as returned by the Klipy CRM API. This typically includes all the company's fields after the update operation, reflecting the latest state.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Klipy CRM API.
- The base URL for the Klipy API must be configured in the credentials.
- Uses HTTP PATCH requests to update company data on the remote service.
Troubleshooting
- Missing or invalid API key: The node will fail if the API key is not provided or incorrect. Ensure the API key credential is properly set up.
- Invalid Company ID: If the specified company ID does not exist or is malformed, the API will return an error. Verify the company ID before running the node.
- Malformed input data: Fields like "Alternative Industries" and "Tags" must be comma-separated strings; improper formatting may cause unexpected results.
- Empty required fields: While updating, some fields are optional, but ensure that the Company ID is always provided.
- API Base URL missing: The node requires a valid base URL from credentials; missing or empty base URL will cause an error.
Links and References
- Klipy CRM API Documentation (Assumed link, replace with actual if available)
- n8n Documentation on Creating Custom Nodes