Description
n8n-nodes-robotframework
This is an n8n community node that enables you to execute Robot Framework scripts directly within your n8n workflows, combining the power of low-code automation with advanced test and robotic process automation (RPA).
n8n is a low-code workflow automation tool similar to Zapier and Make, designed to automate complex workflows with ease. Robot Framework is a versatile automation framework widely used for robotic process automation (RPA), acceptance testing, and more. This node bridges the two systems, allowing seamless execution of Robot Framework scripts inside n8n workflows.
One of the most exciting use cases of this integration is with the Robot Framework Browser library, which supports UI-based interactions like user clicks and website automation without requiring a GUI system environment — everything runs smoothly inside a Docker container housing both n8n and the Robot Framework node.
Installation
This guide walks you through setting up the Robot Framework Node in n8n and running n8n locally using a Docker container. You can follow either the Quick Start or Detailed Instructions, based on your preference.
Quick Navigation
- Quick Start
- Detailed Instructions
- Installing Community Node
—
Quick Start
To quickly set up, ensure Docker is installed, then run the following command:
docker run -it --rm --name n8n -p 5678:5678 -v n8ndata:/home/node/.n8n delilovic/n8nrobotframework:latest
Once the container is up and running, you will see the following message in the terminal:
Editor is now accessible via:
http://localhost:5678/
Open this URL in your browser to start using n8n. Next, follow the Installing Community Node section to add the Robot Framework Node.
—
Detailed Instructions
#### Using the Default n8n Docker Image (Not Recommended)
The default Docker image for n8n is based on Alpine Linux. To set it up, you can refer to the official installation guide: Official n8n Docker Installation Guide.
By default, the Alpine-based Docker image does not include Python and Robot Framework pre-installed. Users need to manually install these dependencies. It has been verified that after installing these dependencies, the Robot Framework node becomes fully functional and ready for use.
Please ensure Python and Robot Framework are installed inside the Docker container before proceeding.
#### Using the Custom n8n_robotframework Docker Image (Recommended)
If you are using the Robot Framework Browser Library, you’ll need the custom Docker image n8n_robotframework, which is based on Debian Bullseye. This custom image includes pre-installed dependencies, such as Python, Robot Framework, and the Browser Library.
This setup ensures that the Robot Framework community node works out of the box.
1. Replace the default image in your setup:
docker.n8n.io/n8nio/n8n
with:
delilovic/n8n_robotframework:latest
2. To run the custom Docker container, execute:
docker run -it --rm --name n8n2 -p 5678:5678 -v n8ndata:/home/node/.n8n delilovic/n8nrobotframework:latest
Once the container is up and running, you will see the following message in the terminal:
Editor is now accessible via:
http://localhost:5678/
Open this URL in your browser to start using n8n. Then proceed to the next step, Installing Community Node, to add the Robot Framework Node.
—
Installing Community Node
After setting up n8n (via either Quick Start or Detailed Instructions), follow these steps:
1. Access Settings:
– Navigate to n8n settings in your instance.
2. Open Community Node Section:
– Go to Community Nodes.
3. Install Robot Framework Node:
– Click the Install button and enter:
n8n-nodes-robotframework
– Confirm the installation.
4. Refresh the Page:
– Refresh your browser window to apply the changes.
5. Start Using the Node:
– The Robot Framework Node will now be available in your n8n workflow editor.
—
About the Custom n8n_robotframework Image
The custom Docker image, n8n_robotframework, is regularly updated alongside major versions of n8n (e.g., 1.72.0, 1.73.0, etc.). It is specifically designed to support the Robot Framework and its Browser Library while requiring minimal changes to the original image.
Additionally, the Robot Framework and the Browser Library are automatically updated to their latest versions every time the build runs for new n8n major versions.
You can access its source code or contribute at this GitHub repository:
GitHub Repository – Custom n8n Robot Framework Image
Usage Example
In this example, we will demonstrate the capabilities of n8n and Robot Framework with a simple yet powerful use case: performing a user login on a website and validating that the user is logged in successfully.
The example highlights the ability to interact with websites, capture screenshots, and maintain browser context while executing workflows across multiple nodes. Each node represents a separate execution.
Additionally, we will showcase how to export the Robot Framework’s report files and pass variables between nodes seamlessly.
Overview
!loginnode.png”>2loginnode.png
When we open the Login node, we see the Robot Framework script area, where the code for automating the login process is written. In this example, we have selected the Include Log HTML option to ensure an execution report (log.html) is generated after the script runs.
As the node has already been executed, the log.html file is now available for download on the Output panel, providing a detailed log of the execution.
There is also an option to toggle Include Other Input Fields, which would pass variables from the previous node to the script. However, since the previous node is a trigger node without any relevant data to pass, this option has been left disabled.
!loginnodereport.png”>4loginnodereport.png
The log.html report file displays the standard Robot Framework execution report. It includes details such as the execution status (PASS), the steps performed (e.g., opening a new browser, navigating to the URL, and entering credentials), and the time taken for each step.
Additionally, as defined in the code, the report includes the screenshot taken just before pressing the login button. This provides a visual confirmation of the login page and the filled-in credentials at the time of execution, making it easier to verify and debug the automation process.
Validate Node Details
!validatenodecode.png”>6validatenodecode.png
In the Validate Login node, we use the Expression View, which allows us to dynamically reference JavaScript expressions and variables from the previous node. Instead of hardcoding values, we utilize variables such as {{ $json.currenturl }} and {{ $json.statefile }}. On the right side, we can see how these expressions are evaluated after the node is executed, as the variables and their values are now known to the editor.
This implementation reuses the browser context state_file from the previous node, enabling the browser to resume exactly where it left off. The workflow navigates to the saved URL and verifies the presence of a specific label (“Secure Area page for Automation Testing Practice”) that appears only after a successful login. Additionally, the workflow captures a screenshot, which is sent via Telegram. The screenshot’s file path is passed to the next node using the Log keyword.
By combining the use of variables from the previous node with runtime evaluations, this approach enhances the workflow’s flexibility and adaptability to various inputs and scenarios.
!telegramnode.png”>8telegramnode.png
Finally, the Telegram node demonstrates how seamlessly Robot Framework can integrate with other n8n nodes, such as AWS, OpenAI, Airtable, and many more.
In this example, the screenshot binary, which was read from disk in the previous node, is dynamically used in the Telegram node. The binary data is sent as a photo attachment, along with a caption reading: “Login was successful!”.
This setup highlights how easily you can combine Robot Framework automation with powerful integrations in n8n to create end-to-end workflows. By leveraging the ability to process files, interact with external APIs, and send notifications, n8n provides a seamless way to share updates across channels. The output panel confirms the successful delivery of the photo and caption to the Telegram channel, completing the workflow.
Importing This Example into Your n8n Instance
You can import this example into your n8n instance by following these steps:
1. Create an empty workflow in your n8n instance.
2. Open the workflow editor and click on the three dots ... at the top right.
3. Select Import from File from the dropdown menu.
4. Upload the
This Week's Favorites in automation
More in automation
Popular Tutorials
AI phone receptionist
JaneJack
An AI receptionist that answers your business calls 24/7, books appointments and handles customer questions.
Meet Jane
Always-on Steam broadcasts
247 Streamer
How to keep a Steam store page broadcast on air around the clock: what Valve allows, the options and real costs.
Keep your page live
.%20In%20this%20example,%20the%20Browser%20Library%20is%20used%20to%20perform%20the%20following%20actions:/plistrongFailure%20Handling:/strong%20The%20task%20begins%20by%20registering%20codeTake%20Screenshot/code%20(with%20the%20codeEMBED/code%20argument)%20as%20the%20failure%20handler%20using%20codeRegister%20Keyword%20To%20Run%20On%20Failure/code.%20This%20ensures%20that%20a%20screenshot%20is%20automatically%20captured%20and%20embedded%20into%20the%20log%20in%20case%20any%20step%20during%20the%20execution%20fails.%20This%20is%20particularly%20useful%20for%20debugging%20issues%20in%20automated%20workflows./liliOpen%20a%20new%20browser%20instance%20in%20headless%20mode%20with%20a%20registered%20codeuserAgent/code./liliNavigate%20to%20the%20login%20page%20using%20the%20code$URL/code%20defined%20in%20the%20variables%20section./liliWait%20for%20the%20cookie%20consent%20modal%20(codediv.fc-consent-root/code)%20to%20be%20hidden%20before%20proceeding./liliEnter%20the%20username%20(code$USERNAME/code)%20and%20password%20(code$PASSWORD/code)%20into%20their%20respective%20input%20fields./liliCapture%20a%20full-page%20screenshot%20during%20the%20login%20process,%20embedded%20directly%20into%20the%20log%20for%20easier%20debugging%20or%20verification./liliClick%20on%20the%20login%20button%20to%20authenticate./liliSave%20the%20current%20URL%20(code$currentemurl/code)%20and%20browser%20state%20(code$state/emfile/code)%20to%20maintain%20session%20continuity%20across%20nodes./liliClose%20the%20browser%20instance%20once%20the%20actions%20are%20complete./liliLog%20both%20the%20current%20URL%20and%20the%20saved%20browser%20state%20for%20reuse%20in%20subsequent%20nodes./lih3Key%20Notes:/h3listrongFailure%20Handling/strong:%20The%20codeRegister%20Keyword%20To%20Run%20On%20Failure/code%20ensures%20screenshots%20(codeTake%20Screenshot/code)%20are%20automatically%20captured%20and%20embedded%20into%20the%20logs%20if%20any%20failure%20occurs%20during%20execution.%20This%20is%20done%20by%20passing%20the%20codeEMBED/code%20argument,%20making%20the%20logs%20more%20informative%20and%20accessible%20directly%20from%20the%20report./lilistrongSession%20Continuity:/strong%20The%20use%20of%20code$state_file/code%20ensures%20session%20continuity.%20This%20allows%20the%20strongValidate%20Login/strong%20node%20to%20resume%20exactly%20where%20the%20strongLogin/strong%20node%20left%20off,%20avoiding%20the%20need%20for%20reauthentication./lilistrongUser-Agent%20Configuration:/strong%20A%20custom%20codeuserAgent/code%20is%20passed%20via%20codeNew%20Context/code,%20simulating%20a%20specific%20browser%20environment%20(codeMozilla/5.0...Chrome/124.0...Safari/537.36/code),%20which%20is%20helpful%20for%20compatibility%20testing./lipVariables%20in%20the%20Robot%20Framework%20node%20are%20no%20longer%20automatically%20forwarded%20between%20nodes.%20Instead,%20variables%20must%20explicitly%20be%20passed%20to%20subsequent%20nodes%20using%20the%20codeLog/code%20keyword%20(e.g.,%20codeLog%20$foo/code).%20This%20approach%20ensures%20that%20only%20the%20intended%20variables%20are%20available%20to%20downstream%20nodes,%20improving%20efficiency%20and%20clarity%20within%20workflows./ppAdditionally,%20the%20Robot%20Framework’s%20standard%20output%20is%20automatically%20included,%20providing%20the%20framework’s%20typical%20execution%20status%20and%20result%20details./pp!a%20href=){kind=link}
