Klipy
Actions13
Overview
This node integrates with the Klipy CRM API to manage company records. Specifically, the Create Company operation allows users to add new companies into their Klipy CRM database by providing detailed company information such as name, domain, description, industry tags, contact details, and social media links.
Typical use cases include:
- Automating the addition of new business leads or partners into a CRM system.
- Enriching company data in workflows that gather information from external sources.
- Streamlining onboarding processes by programmatically creating company profiles.
For example, a marketing automation workflow could create a new company record whenever a lead form is submitted on a website, ensuring the CRM stays up-to-date without manual entry.
Properties
| Name | Meaning |
|---|---|
| Name | The official name of the company (required). |
| Domain | The company's internet domain (required). |
| Description | A textual description of the company. |
| Alternative Industries | Comma-separated list of alternative industries the company operates in (e.g., "Software, AI, Technology"). |
| Tags | Comma-separated list of tags for categorization (e.g., "enterprise, b2b, startup"). |
| Founded Year | The year the company was founded (numeric). |
| Address | Street address of the company. |
| City | City where the company is located. |
| State | State or region of the company. |
| Country | Country of the company. |
| Phone | Contact phone number. |
| URL or identifier for the company's LinkedIn profile. | |
| URL or handle for the company's Twitter account. | |
| URL or identifier for the company's Facebook page. | |
| URL or handle for the company's Instagram profile. | |
| Crunchbase | URL or identifier for the company's Crunchbase profile. |
| Remarks | Additional notes or remarks about the company. |
Output
The node outputs JSON data representing the newly created company record as returned by the Klipy CRM API. This typically includes all the fields sent during creation along with any additional metadata assigned by the API, such as unique company ID, timestamps, or status.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Klipy CRM API.
- The base URL for the Klipy API must be configured in the credentials.
- Uses HTTP requests (GET, POST, PATCH, DELETE) via Axios library internally.
- Proper network access to the Klipy API endpoint is necessary.
Troubleshooting
- Missing Base URL or API Key: The node will throw an error if the base URL or API key is not set or empty in the credentials. Ensure these are correctly configured.
- Required Fields Not Provided: The
nameanddomainfields are mandatory for creating a company. Omitting them will likely cause API errors. - Invalid Format for Alternative Industries or Tags: These fields expect comma-separated strings; improper formatting may result in unexpected behavior.
- API Errors: If the API returns an error (e.g., authentication failure, validation error), the node will throw an error unless "Continue On Fail" is enabled, in which case the error message is included in the output.
- Network Issues: Connectivity problems to the Klipy API endpoint will cause request failures.
Links and References
- Klipy CRM API Documentation (hypothetical link, replace with actual if available)
- n8n Documentation on Creating Custom Nodes
- Axios HTTP Client