How to connect Getresponse and Recruitee
Create a New Scenario to Connect Getresponse and Recruitee
In the workspace, click the “Create New Scenario” button.

Add the First Step
Add the first node – a trigger that will initiate the scenario when it receives the required event. Triggers can be scheduled, called by a Getresponse, triggered by another scenario, or executed manually (for testing purposes). In most cases, Getresponse or Recruitee will be your first step. To do this, click "Choose an app," find Getresponse or Recruitee, and select the appropriate trigger to start the scenario.

Add the Getresponse Node
Select the Getresponse node from the app selection panel on the right.


Getresponse

Configure the Getresponse
Click on the Getresponse node to configure it. You can modify the Getresponse URL and choose between DEV and PROD versions. You can also copy it for use in further automations.
Add the Recruitee Node
Next, click the plus (+) icon on the Getresponse node, select Recruitee from the list of available apps, and choose the action you need from the list of nodes within Recruitee.


Getresponse
⚙
Recruitee

Authenticate Recruitee
Now, click the Recruitee node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Recruitee settings. Authentication allows you to use Recruitee through Latenode.
Configure the Getresponse and Recruitee Nodes
Next, configure the nodes by filling in the required parameters according to your logic. Fields marked with a red asterisk (*) are mandatory.
Set Up the Getresponse and Recruitee Integration
Use various Latenode nodes to transform data and enhance your integration:
- Branching: Create multiple branches within the scenario to handle complex logic.
- Merging: Combine different node branches into one, passing data through it.
- Plug n Play Nodes: Use nodes that don’t require account credentials.
- Ask AI: Use the GPT-powered option to add AI capabilities to any node.
- Wait: Set waiting times, either for intervals or until specific dates.
- Sub-scenarios (Nodules): Create sub-scenarios that are encapsulated in a single node.
- Iteration: Process arrays of data when needed.
- Code: Write custom code or ask our AI assistant to do it for you.

JavaScript
⚙
AI Anthropic Claude 3
⚙
Recruitee
Trigger on Webhook
⚙

Getresponse
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring Getresponse, Recruitee, and any additional nodes, don’t forget to save the scenario and click "Deploy." Activating the scenario ensures it will run automatically whenever the trigger node receives input or a condition is met. By default, all newly created scenarios are deactivated.
Test the Scenario
Run the scenario by clicking “Run once” and triggering an event to check if the Getresponse and Recruitee integration works as expected. Depending on your setup, data should flow between Getresponse and Recruitee (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Getresponse and Recruitee
Getresponse + Recruitee + Slack: When a new contact is added to Getresponse, the automation searches for a matching candidate in Recruitee. If a match is found, a Slack notification is sent to the recruitment team.
Recruitee + Getresponse + Google Sheets: When a new candidate is added to Recruitee, their information is added as a contact in Getresponse and also logged as a new row in a Google Sheet for tracking purposes.
Getresponse and Recruitee integration alternatives

About Getresponse
Use Getresponse in Latenode to automate email marketing tasks within larger workflows. Trigger campaigns based on data from your CRM, database, or other apps. Latenode lets you customize logic with JavaScript or AI, parse data, and control the entire flow visually. Send targeted emails based on user actions.
Similar apps
Related categories
About Recruitee
Automate your hiring process with Recruitee in Latenode. Trigger workflows on new applications to screen candidates, send automated messages, and update other systems. Connect Recruitee to HR tools for seamless data flow and custom talent pipelines. Simplify recruiting tasks using Latenode's visual editor and scaling options.
Related categories
See how Latenode works
FAQ Getresponse and Recruitee
How can I connect my Getresponse account to Recruitee using Latenode?
To connect your Getresponse account to Recruitee on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Getresponse and click on "Connect".
- Authenticate your Getresponse and Recruitee accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically add new hires to my email list?
Yes, you can! Latenode allows seamless data transfer, automatically adding new Recruitee hires to Getresponse lists. This nurtures talent with personalized onboarding and updates.
What types of tasks can I perform by integrating Getresponse with Recruitee?
Integrating Getresponse with Recruitee allows you to perform various tasks, including:
- Add new candidates to Getresponse for automated nurturing campaigns.
- Trigger email sequences in Getresponse when a candidate reaches a specific stage in Recruitee.
- Update candidate information in Getresponse based on Recruitee profile changes.
- Send personalized offer letters via Getresponse triggered by Recruitee offer approval.
- Segment candidates in Getresponse based on Recruitee job applied for or department.
What Getresponse events can trigger workflows inside Latenode?
Getresponse events like new subscriptions, campaign opens, and clicks can trigger Latenode workflows, automating tasks across various connected apps.
Are there any limitations to the Getresponse and Recruitee integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex data transformations may require JavaScript or AI blocks.
- Rate limits on the Getresponse and Recruitee APIs may affect performance.
- Historical data migration requires manual configuration.