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 company data. Specifically, the "Company" resource with the "Get" operation allows users to retrieve detailed information about a specific company by its unique ID. This is useful in scenarios where you want to fetch up-to-date company details from your CRM system for further processing, reporting, or automation workflows.

Practical examples include:

  • Fetching company details before creating related records like contacts or interactions.
  • Enriching customer data in other systems by pulling company info dynamically.
  • Validating company existence and retrieving metadata during lead qualification processes.

Properties

Name Meaning
Company ID The unique identifier of the company to retrieve. This is a required string input.

Output

The node outputs a JSON object representing the company data retrieved from the Klipy CRM API. The structure typically includes fields such as company name, domain, description, industry tags, founded year, address details, social media links, phone number, and remarks.

If multiple companies were returned (not applicable for "Get" by ID), it would output an array of such objects. However, for this operation, the output is a single company object.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Klipy CRM API.
  • Needs an API key credential configured in n8n to authenticate requests.
  • The base URL for the Klipy API must be set in the credentials.
  • Uses HTTP GET requests to fetch company data.

Troubleshooting

  • Missing or invalid Company ID: Ensure that the "Company ID" property is provided and correctly corresponds to an existing company in Klipy CRM.
  • Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
  • Base URL not set: The node will throw an error if the base URL is missing or empty in the credentials.
  • Network issues or API downtime: Check network connectivity and Klipy service status if requests fail.
  • Error messages from API: These are passed through; review the message for clues (e.g., "Not Found" if company ID does not exist).

To resolve common errors:

  • Double-check the company ID format.
  • Confirm API key validity and permissions.
  • Ensure the base URL ends with a slash or is properly formatted.
  • Use the "Test API Key" operation under the "Auth" resource to verify connectivity.

Links and References

Discussion