GetResponse Contact Segmentation and Campaign Update - n8n Workflow

Use this powerful n8n workflow to fetch all contacts from GetResponse, filter based on their current campaign, and selectively update their campaign membership using core logic n8n nodes.

Workflow Preview

Ready to automate?

Download this n8n workflow template and start using it instantly.

Who is this best for?

Email Marketing Specialists needing bulk list segmentation.
CRM Administrators who frequently migrate contacts between campaigns.
Users looking for reliable n8n templates for large data manipulation.
Anyone needing an n8n workflow to manage GetResponse contacts programmatically.

Overview

Managing large subscriber lists across multiple campaigns can be time-consuming and prone to errors. This specific n8n workflow solves the problem of targeted contact migration by efficiently retrieving all contacts from GetResponse and applying sophisticated filtering logic before updating their records. This ensures that only relevant contacts—those not already belonging to a specific exclusion campaign (e.g., 'n8n' in this example)—are moved to the new target campaign ID. This reliable n8n workflow provides a solid foundation for complex email automation and list hygiene.

How it Works

This automation is initiated by a manual n8n trigger, making it easy to run on-demand for list cleanups or migrations.


  1. Trigger Execution: The n8n workflow starts when the 'On clicking 'execute'' n8n trigger is activated.

  2. Fetch All Contacts: The first GetResponse n8n node queries the platform to retrieve all available contacts, ensuring that no contact is missed.

  3. Conditional Filtering (IF n8n node): Each contact item is passed to the IF n8n node. This node checks if the contact's current campaign name is not equal to 'n8n'. This acts as a safeguard, ensuring contacts already classified or segmented into the 'n8n' campaign are excluded from the update process.

  4. Update Contact (True Path): If the contact's campaign is not 'n8n', the workflow proceeds down the true path to the second GetResponse n8n node. This n8n node takes the contact's ID and updates their record, moving them into the target campaign defined by the fixed Campaign ID (WRVXO).

  5. Skip (False Path): If the contact's campaign is 'n8n', the workflow proceeds down the false path to the NoOp n8n node, which halts processing for that specific item, successfully filtering it out of the update action. This systematic approach showcases the power of structured n8n templates for CRM operations.

Installation Guide

To deploy this powerful n8n workflow, follow these steps:


  1. Import: Copy the provided JSON code and paste it into your n8n instance using the 'New' -> 'Import from JSON' function.

  2. Credentials: Locate the 'GetResponse' and 'GetResponse1' n8n node. You must set up a GetResponse API credential for each. Click the 'Credentials' section and connect your GetResponse API key.

  3. Customization: Edit the logic in the 'IF' n8n node if you need to filter contacts based on a different exclusion campaign name (currently set to 'n8n').

  4. Target Campaign: In the 'GetResponse1' n8n node, update the campaignId parameter (currently WRVXO) to match the desired target campaign ID you wish to move contacts into.

  5. Execution: Save the n8n workflow. Since the n8n trigger is manual, you can test it item-by-item or execute the entire n8n workflow to process all contacts.

Node Details

This n8n workflow leverages four key functional nodes to achieve its goal:

On clicking 'execute' (Manual Trigger): The essential n8n trigger that initiates the entire automation. Ideal for testing and scheduled manual execution of this n8n templates solution.
GetResponse (n8n node): Function: Retrieves all existing contacts from the GetResponse platform. Key Configuration: Operation: getAll, Return All: true.
IF (n8n node): Function: Filters the list of contacts based on their current campaign membership. Only contacts whose campaign name is not equal to 'n8n' pass to the True branch. Key Configuration: Checks if $node["GetResponse"].json["campaign"]["name"] is notEqual to 'n8n'.
GetResponse1 (n8n node): Function: Updates the specific contact record that passed the IF condition. Key Configuration: Operation: update, sets the campaignId to WRVXO using the filtered contact's ID.


  • NoOp (n8n node): Function: Acts as the terminal node for the False branch, cleanly stopping the execution for contacts that should be filtered out.

Related n8n Workflows

Free

Nodes: 4 Nodes
Updated: December 26 2025
View all
Created by
ghagrawal17
ghagrawal17

Featured*