Klipy
Actions13
Overview
This node integrates with the Klipy CRM API to manage "Person" records, specifically allowing you to update an existing person's details. It is useful in scenarios where you need to keep your CRM data current by modifying contact information such as email, phone numbers, social media links, company affiliation, job title, and remarks.
For example, if a contact changes their phone number or job title, this node can update those fields in Klipy CRM automatically from your workflow, ensuring your CRM always has the latest information.
Properties
| Name | Meaning |
|---|---|
| Person ID | The unique identifier of the person record to update. |
| Person Data | The set of fields to update for the person, including: |
| - Type: Type of person (e.g., email, phone) | |
| - Identifier: Email address or phone number | |
| - First Name | |
| - Last Name | |
| - Phone | |
| - Personal Phone | |
| - Company | |
| - Title | |
| - Remarks (multi-line text) |
Output
The node outputs the updated person object returned by the Klipy CRM API in JSON format. This typically includes all the person's fields after the update, reflecting the new state of the record.
No binary data output is produced by this operation.
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 person data via the Klipy REST API.
Troubleshooting
- Missing Base URL or API Key: The node will throw an error if the base URL or API key is not provided or empty in the credentials.
- Invalid Person ID: If the specified Person ID does not exist, the API may return an error indicating the resource was not found.
- Invalid Field Values: Ensure that fields like email or phone are correctly formatted; otherwise, the API might reject the update.
- API Errors: Network issues or invalid API keys will cause request failures. Verify connectivity and credential validity.
- Continue on Fail: If enabled, errors for individual items will be captured in the output instead of stopping execution.
Links and References
- Klipy CRM API Documentation (Assumed URL, replace with actual if available)