Klipy icon

Klipy

Interact with Klipy CRM API to manage contacts, companies, and interactions. Can be used as an AI tool for CRM operations.
Join our community

Actions13

Overview

The "Person Upsert" operation in this node interacts with the Klipy CRM API to either update an existing person record or create a new one if it does not exist, based on the provided email address. This operation is useful for synchronizing contact data where you want to ensure that a person's information is present and up-to-date without manually checking if the record exists.

Common scenarios include:

  • Importing or syncing contacts from other systems where duplicates should be avoided.
  • Automatically updating contact details when new information becomes available.
  • Creating new contacts on-the-fly during lead generation or customer onboarding workflows.

For example, you can provide an email and optionally other personal details like first name, last name, phone numbers, social media links, company, title, and remarks. The node will then send this data to Klipy CRM, which will either update the existing person with that email or create a new person record.

Properties

Name Meaning
Email The email address of the person; required and used as the unique identifier for upsert.
First Name The person's first name.
Last Name The person's last name.
Phone The person's primary phone number.
Personal Phone An additional personal phone number for the person.
LinkedIn URL or handle of the person's LinkedIn profile.
Twitter URL or handle of the person's Twitter profile.
Facebook URL or handle of the person's Facebook profile.
Instagram URL or handle of the person's Instagram profile.
WhatsApp The person's WhatsApp contact number.
Company The company name associated with the person.
Title The person's job title or position.
Remarks Additional notes or remarks about the person (multi-line text).

Output

The output JSON contains the response from the Klipy CRM API after performing the upsert operation. This typically includes the full person object as stored in the CRM, such as the assigned ID, all submitted fields, timestamps, and any additional metadata returned by the API.

The node does not output binary data.

Dependencies

  • Requires an active connection to the Klipy CRM API.
  • Requires an API key credential configured in n8n for authentication.
  • The base URL for the Klipy API must be set in the credentials.
  • Uses HTTP PUT method to perform the upsert via the endpoint /people.

Troubleshooting

  • Missing Email Error: If the email field is empty or missing, the node throws an error: "Email is required for upsert operation". Ensure the email property is provided and not empty.
  • Invalid Email Format: If the email does not match a valid email pattern, the node throws: "Email must be a valid email address for upsert operation". Validate the email format before running the node.
  • API Connection Issues: Errors related to authentication or network connectivity may occur if the API key or base URL is incorrect or missing.
  • Unexpected API Response: If the API returns an error, the node will throw it unless "Continue On Fail" is enabled, in which case the error message will be included in the output.

Links and References

Discussion