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, which are records of communications or events related to contacts or companies. Specifically, the "Get" operation for the "Interaction" resource retrieves a single interaction by its unique ID.

Use cases include:

  • Fetching detailed information about a specific interaction such as an email, call, meeting, or note.
  • Accessing historical communication data linked to contacts or companies in your CRM.
  • Automating workflows that require retrieving interaction details for further processing or reporting.

For example, you might use this node to get the details of a customer call logged in Klipy CRM and then trigger follow-up actions based on the interaction content.

Properties

Name Meaning
Interaction ID The unique identifier of the interaction to retrieve. This is required to specify which interaction record to fetch from the CRM.

Output

The node outputs JSON data representing the interaction object retrieved from the Klipy CRM API. The structure typically includes fields describing the interaction type (e.g., email, call), direction (inbound/outbound), associated contacts or companies, title, summary, date/time, and other metadata.

No binary data output is produced by this operation.

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 GET requests to fetch interaction data from the endpoint: {baseUrl}/interactions/{interactionId}.

Troubleshooting

  • Missing or invalid Interaction ID: Ensure the Interaction ID property is provided and correctly formatted; otherwise, the API will return an error.
  • Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
  • Base URL not set: The node throws an error if the base URL is missing or empty in the credentials.
  • API request failures: Network issues or incorrect IDs may cause request failures. Check the error messages returned and confirm the interaction exists.
  • If the node is set to continue on failure, errors will be returned as part of the output JSON with an error field.

Links and References

Discussion