Skip to main content

R5.5.3: Connecting Klipy with n8n

Build powerful, node-based workflows with Klipy and n8n. This guide covers setting up triggers, performing actions, and leveraging n8n's flexibility for custom automation.

Jung Hong Kim avatar
Written by Jung Hong Kim
Updated over 2 weeks ago


n8n is a powerful, source-available workflow automation tool that empowers you to connect APIs and build complex automations with its visual, node-based editor. A key advantage of n8n is its flexibility; you can use their cloud service or self-host the entire platform for complete data privacy and control.

Klipy integrates with n8n using its core building blocks: the Webhook node for receiving triggers from Klipy, and the HTTP Request node for performing actions in Klipy.

This gives you direct access to the Klipy API within n8n's robust framework.

Prerequisites

  • An active Klipy account with permissions to access settings.

  • An active n8n instance (either on n8n Cloud or self-hosted).

  • The Klipy API Documentation for reference on API endpoints and data structures.

Step 1: Get Your Klipy API Key

You'll need an API Key to authorize n8n to perform actions in your Klipy account.

  1. Log in to your Klipy account.

  2. Navigate to Settings > API.

  3. Click "Generate New Key".

  4. Give the key a descriptive name, like "n8n Integration," and click "Create".

  5. Important: Copy this key immediately and store it in a secure place. For security, you will not be able to see this key again after closing the window.

Step 2: Building Your First Workflow (Trigger from Klipy)

Let's create a workflow that starts when something happens in Klipy.
​Example: When a deal stage is moved in Klipy, use an IF node to check if the new stage is "Negotiation" and, if so, send an email notification.
​

Part A: Set up the Trigger (Webhook Node)

  1. In your n8n canvas, click the + icon to add your first node.

  2. Search for and select the Webhook node.

  3. The node properties will appear on the right. In the "Webhook URLs" section, copy the TEST URL.

  4. Go to your Klipy account and navigate to Settings > Webhooks.

  5. Click "Add Endpoint", paste the copied TEST URL into the "Endpoint URL" field, and give it a name.

  6. In the "Events to send" list, check the box for deal.moved. Click "Save".

  7. Return to n8n and click the "Listen for test event" button.

  8. In Klipy, move a test deal into a new stage. n8n will show a notification when it receives the data, which will then be available for use in subsequent nodes.

Part B: Add Conditional Logic (IF Node)

  1. Click the + icon on the Webhook node to add the next node.

  2. Search for and select the IF node.

  3. Click "Add Condition". Configure it to check the incoming data:

    • Value 1: Click the "target" icon, navigate to Current Node > Input Data > JSON > body > stage_name. This will insert an expression like {{$json["body"]["stage_name"]}}.

    • Operation: String > Contains

    • Value 2: Negotiation

This node now has two outputs: true and false. The workflow will only proceed down the true path if the deal's new stage name contains "Negotiation".

Part C: Set up the Action (Send Email)

  1. Click the + icon on the true output of the IF node.

  2. Search for and add an email node (e.g., Send Email, Gmail, or Microsoft Outlook).

  3. Configure the email, using expressions to pull data from the trigger:

    • To: Enter the recipient's email address.

    • Subject: Deal Entered Negotiation: {{$json["body"]["deal_name"]}}

    • Text: Craft a message, for example: The deal "{{$json["body"]["deal_name"]}}" has moved to the negotiation stage. Please follow up.

Step 3: Performing Actions in Klipy (HTTP Request Node)

Now let's create a workflow that performs an action in Klipy.
​Example: When a new contact is created in HubSpot, create a corresponding contact in Klipy.
​

Part A: Create a Reusable Credential (Recommended Best Practice)

Storing your API key as a credential in n8n is more secure and reusable.

  1. In your n8n sidebar, go to Credentials > Add credential.

  2. Search for and select Header Auth.

  3. Credential Name: Klipy API Key

  4. Name: Authorization

  5. Value: Bearer YOUR_API_KEY (Replace YOUR_API_KEY with the key you generated in Step 1).

  6. Click "Save".

Part B: Configure the Workflow

  1. Start a new workflow with a trigger node for your other app (e.g., HubSpot Trigger for "Contact Created").

  2. Add the next node by clicking the + icon. Search for and select the HTTP Request node.

  3. Configure the node properties:

    • Authentication: Select Header Auth from the dropdown.

    • Credential for Header Auth: Select the Klipy API Key credential you just created.

    • Method: POST

    • URL: https://api.klipy.ai/api/v1/people (Always check the official Klipy API documentation for the correct endpoint).

    • Send Body: true

    • Body Content Type: JSON

    • JSON Parameters:

      • Click "Add Property".

      • Property Name: name

      • Value: Use an expression to combine the first and last name from the HubSpot trigger: {{$json["properties"]["firstname"]}} {{$json["properties"]["lastname"]}}

      • Click "Add Property" again.

      • Property Name: email

      • Value: Use an expression to map the email: {{$json["properties"]["email"]}}

Step 4: Activating Your Workflow

  1. Testing: Use the "Execute Workflow" button to run the workflow with test data.

  2. Activation: Once you are satisfied with the result, activate the workflow by toggling the Active switch at the top-left of the screen.

  3. Important for Webhooks: For webhook-triggered workflows, you must now go back to the Webhook node, copy the PRODUCTION URL, and update the endpoint in your Klipy settings (Settings > Webhooks). Test URLs only work when you are actively listening in the editor.

Your n8n workflow is now live and will run automatically.

Navigation:

Related Articles
R5.6.1: Getting Started with Webhooks for Custom Workflows
R5.5: Workflow Automation (Zapier, Make, n8n)
R5.5.1: Connecting Klipy with Zapier
R5.5.2: Connecting Klipy with Make
Did this answer your question?