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, people, companies, and authentication. Specifically, for the Interaction - Get All operation, it retrieves a list of interaction records from the Klipy CRM system. This is useful for scenarios where you want to fetch multiple interactions, possibly filtered by company or contact, and paginate through large datasets.

Practical examples include:

  • Fetching all recent customer interactions for analysis or reporting.
  • Retrieving interactions related to a specific company or contact to display in a dashboard.
  • Automating workflows that trigger based on new or updated interactions.

Properties

Name Meaning
Cursor Cursor string used for pagination to continue fetching results from where the last call ended.
Limit Maximum number of interaction records to return in one request (default 20).
Company ID Filter interactions to only those associated with a specific company ID.
Contact ID Filter interactions to only those associated with a specific contact ID.

Output

The output is a JSON array containing interaction objects as returned by the Klipy CRM API. Each object represents an interaction record with details such as type, direction, involved entities, title, summary, date, and main contact information.

If multiple interactions are returned, they are flattened into a single array. If only one interaction is returned, it is wrapped in an array for consistency.

The node does not output binary data.

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 requests via Axios to communicate with the Klipy API endpoints.

Troubleshooting

  • Missing Base URL or API Key: The node will throw an error if the base URL or API key is missing or empty in the credentials. Ensure these are correctly set.
  • Invalid Filters: Providing invalid company or contact IDs may result in empty responses or errors from the API.
  • Pagination Issues: If the cursor parameter is incorrect or expired, pagination may fail or return unexpected results.
  • API Errors: Network issues or API downtime can cause request failures. Check connectivity and API status.
  • Error Handling: If "Continue On Fail" is enabled, errors for individual items will be returned as objects with an error property instead of stopping execution.

Links and References

Discussion