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

This node integrates with the Klipy CRM API to manage interactions related to contacts and companies. Specifically, the Interaction - Create operation allows users to record a new interaction event such as an email, call, meeting, note, or other types of communication within their CRM system.

Typical use cases include:

  • Logging customer communications automatically after calls or emails.
  • Tracking meetings or events associated with specific contacts or companies.
  • Adding notes or summaries about interactions for future reference.
  • Associating interactions with primary and secondary entities (persons or companies) in the CRM.

For example, after a sales call, you could create an interaction entry with details like type "call", direction "outbound", the contact involved, date/time, and a summary of the discussion.

Properties

Name Meaning
Type Type of interaction (e.g., email, call, meeting, note).
Direction Direction of interaction. Options: Inbound, Outbound, Hybrid, Internal, Event.
Primary ID Primary entity ID (person or company) associated with the interaction.
Secondary ID Secondary entity ID (person or company) optionally linked to the interaction.
Title Title or subject of the interaction.
Summary Detailed summary or notes about the interaction.
Interaction Date Date and time when the interaction occurred; converted internally to a Unix timestamp.
Main Contact Person ID of the main contact involved (required if Main Contact Email is not provided).
Main Contact Email Email address of the main contact (required if Main Contact ID is not provided).

Output

The node outputs JSON data representing the created interaction object returned by the Klipy CRM API. This typically includes all properties of the newly created interaction such as its unique ID, timestamps, associated entities, and any metadata stored by the CRM.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Klipy CRM API.
  • An API key credential must be configured in n8n to authenticate requests.
  • The base URL for the Klipy API must be set in the credentials.
  • Uses HTTP POST requests to send interaction data to the /interactions endpoint.

Troubleshooting

  • Missing main contact information: The node throws an error if neither mainContact (Person ID) nor mainContactEmail is provided. Ensure at least one is supplied.
  • Invalid date format: The interactionDate should be a valid date/time string convertible to a Unix timestamp.
  • API authentication errors: If the API key or base URL is missing or incorrect, requests will fail. Verify credentials configuration.
  • Network or API errors: Standard HTTP errors from the Klipy API may occur; check the error message for details.
  • Continue on Fail: If enabled, errors for individual items will be captured in the output instead of stopping execution.

Links and References

Discussion