KlipyInstall

Overview

This node integrates with the Klipy CRM API to manage "Person" entities, allowing users to perform various operations such as retrieving a person by ID, listing all people with filters, creating, updating, deleting, and upserting person records. It is useful in scenarios where you want to automate CRM workflows, synchronize contact data, or enrich your contact database programmatically.

For example, you can use this node to:

• Fetch detailed information about a specific person using their unique ID.
• Retrieve a filtered list of people based on email, phone, company affiliation, or owner.
• Create new person records from form submissions or other data sources.
• Update existing contacts with new information.
• Upsert (update or insert) a person record based on their email address, ensuring no duplicates.

Properties

Output

The node outputs JSON data representing the person(s) retrieved or affected by the operation. The structure corresponds directly to the Klipy CRM API's person object schema, including fields like name, contact details, social media links, company association, and remarks.

• For Get operation: Outputs a single person object.
• For Get All operation: Outputs an array of person objects matching the query parameters.
• For Create, Update, Delete, and Upsert operations: Outputs the resulting person object or confirmation response from the API.

No binary data output is produced by this node.

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 methods GET, POST, PATCH, DELETE, and PUT to interact with the API endpoints.
• Axios library is used internally for HTTP requests.

Troubleshooting

• Missing Base URL or API Key: If the base URL or API key is not set or empty in credentials, the node will throw an error indicating that the base URL is required.
• Invalid Person ID: Providing an invalid or non-existent person ID will result in an API error; ensure the ID is correct.
• Email Validation on Upsert: The upsert operation requires a valid email address. If missing or invalid, the node throws an error stating that a valid email is required.
• API Rate Limits or Network Issues: Standard HTTP errors may occur if the API rate limits are exceeded or network connectivity issues arise.
• Continue On Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error messages in the output.

Links and References

• Klipy CRM API Documentation (Assumed URL, replace with actual if available)
• Axios HTTP Client