growthx

Growth-x API integration for n8n

Package Information

Downloads: 1 weekly / 3 monthly
Latest Version: 1.0.0
Author: growth-x

Documentation

n8n-nodes-growthx

This is an n8n community node. It lets you use Growth-X in your n8n workflows.

Growth-X is a sales automation platform that helps you connect with prospects on LinkedIn through AI-powered outreach, campaign management, and CRM integrations.

n8n is a fair-code licensed workflow automation platform.

Installation
Operations
Credentials
Usage
Resources


Installation

Follow the installation guide in the n8n community nodes documentation.

To install this community node:

npm install n8n-nodes-growthx

Operations

This node allows you to interact with Growth-X's receiver and messaging APIs.

Receiver

  • Add Receiver to Campaign
    Assign a LinkedIn contact to a campaign.

  • Remove Receiver from Campaign
    Remove a LinkedIn contact from a campaign.

  • Send Message to Receiver
    Send a direct message to a LinkedIn contact in a campaign.

Each of these operations requires input fields such as:

  • Campaign (select from dynamic list)
  • LinkedIn URL
  • Email (optional)
  • External CRM ID (optional)
  • Message and sender email (for messaging only)

Credentials

To use this node, you need a Growth-X API key.

Steps:

  1. Sign up or log in to Growth-X.
  2. Go to Integrations settings and locate the API TOKEN.
  3. In n8n:
    • Open "Credentials".
    • Click "New" → Select GrowthX API.
    • Paste your API Key into the appropriate field.

Usage

You can integrate Growth-X into workflows such as:

  • Importing LinkedIn leads from a spreadsheet and assigning them to Growth-X campaigns.
  • Automating personalized messaging campaigns on LinkedIn.
  • Keeping Growth-X campaign membership in sync with your CRM or other tools.

Dynamic dropdowns are available for:

  • Campaigns (via getCampaigns)
  • User emails (via getUsers)

Webhook functionality is available through the separate GrowthX Trigger node.

Resources


Contributions, bug reports, and feature requests are welcome via GitHub Issues.

Discussion