Klipy
Interact with Klipy CRM API to manage contacts, companies, and interactions. Can be used as an AI tool for CRM operations.
Actions13
Overview
This node integrates with the Klipy CRM API to manage "Person" entities, specifically allowing creation of new person records. It is useful in scenarios where you want to automate adding contacts to your CRM system from various sources or workflows. For example, when a new lead signs up on your website, this node can create a corresponding person record in Klipy CRM with their contact details and social profiles.
Properties
| Name | Meaning |
|---|---|
| Type | The type of person identifier, e.g., "email" or "phone". |
| Identifier | The actual email address or phone number of the person. |
| First Name | The first name of the person. |
| Last Name | The last name of the person (optional). |
| Phone | A phone number associated with the person (optional). |
| Personal Phone | A personal phone number for the person (optional). |
| LinkedIn profile URL or handle (optional). | |
| Twitter handle (optional). | |
| Facebook profile URL or handle (optional). | |
| Instagram handle (optional). | |
| WhatsApp number or identifier (optional). | |
| Company | The company name the person is associated with (optional). |
| Title | Job title or position of the person (optional). |
| Remarks | Additional notes or remarks about the person (optional). |
Output
The node outputs JSON data representing the created person record as returned by the Klipy CRM API. This typically includes all the fields sent plus any additional metadata or IDs assigned by the CRM system. The output is an array of such JSON objects if multiple inputs are processed.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Klipy CRM API.
- Needs the base URL of the Klipy API configured in credentials.
- Uses HTTP requests via axios library to communicate with the API.
Troubleshooting
- Missing Base URL or API Key: The node will throw an error if the base URL or API key is not set in credentials.
- Validation Errors: If required fields like "Type", "Identifier", or "First Name" are missing, the API may reject the request.
- API Errors: Network issues or invalid API keys will cause HTTP errors; ensure the API key is valid and has necessary permissions.
- Incorrect Data Types: Ensure that fields like "Type" and "Identifier" are strings and properly formatted (e.g., valid email format).
- Continue On Fail: If enabled, the node will continue processing other items even if one fails, returning error messages in the output.
Links and References
- Klipy CRM API Documentation (Assumed, replace with actual link if available)
- n8n Documentation - Creating Custom Nodes