Repo for Robocorp Developer Certification training (Levels 1–3) and some extras.
This is hands-on automation practice using Robocorp’s tools, Control Room, and Python.
Practicing Robocorp automation by completing the official certification levels and doing some weekend projects of my own.
Focus on browser automation, data handling, PDF/report generation, and running robots both locally and in Control Room.
Basic setup and first automation:
- Installed extensions and initialized the repo.
- Launched browser and logged in.
- Downloaded Excel file and read data.
- Filled form based on Excel input.
- Generated PDF from HTML.
- Uploaded to Control Room, ran successfully, and scheduled the process.
Independent robot build according to given requirements:
- Opened robot order website and handled modal dialogs.
- Pulled orders from Control Room asset (orders.csv).
- Looped through orders, filling the form automatically.
- Captured screenshots of receipts.
- Created PDFs and embedded screenshots.
- Archived all receipts into a ZIP.
- Designed to run out-of-the-box both locally and in Control Room.
In Control Room:
- Create an asset named orders.csv with required headers.
- Artifacts (PDFs, screenshots, archive) are collected from output/.
Locally:
- Create assets.json with reference to orders.csv.
Guided work data management build with producer-consumer setup. Steps included:
- Downloading JSON traffic data.
- Producing work items from JSON data.
- Creating a consumer step to process work items.
- Using Control Room to run the producer → consumer chain.
- Understanding best practices for scalable automation pipelines.
This repo will also serve as a sandbox for personal robots beyond the certifications. Experiments, small automations, and side projects.
A weekend project showcasing a producer–consumer process in Robocorp:
- Takes optional input parameters (keywords, time ranges, sort order).
- Producer queries the free international NewsAPI and creates work items.
- Consumer turns each work item into a PDF digest.
- Outputs are archived as run artifacts in Control Room.
- Scheduled to run weekly via Control Room scheduler.
The News Digest process is built as a two-step producer–consumer. Locally you can test both sides using the FileAdapter for work items.
- Create an input work item JSON
Place it underdevdata/work-items-in/test-input-for-consumer/work-items.json:
[
{
"payload": {
"NEWS_KEYWORD": "Porsche",
"FROM_DATE": "YESTERDAY",
"SORT_BY": "popularity"
},
"files": {}
}
]Supported FROM_DATE values: "NOW" / "TODAY" → today’s date "YESTERDAY" / "DAILY" → yesterday "WEEKLY" → 7 days back "MONTHLY" → 30 days back Or provide an explicit "YYYY-MM-DD" string
-
Run the producer
bash Copy code RC_WORKITEM_ADAPTER=FileAdapter rcc run -t produce_news_data This queries the NewsAPI and generates work items under output/work-items. -
Run the consumer
bash Copy code RC_WORKITEM_ADAPTER=FileAdapter rcc run -t consume_news_data This consumes the items and creates a PDF digest into the output/ folder. -
Inspect artifacts
After a Control Room run, the PDF will appear under the run’s Artifacts tab (alongside log.html, console.txt, etc.). Locally, check the output/ folder for News_digest_from.pdf.
This repo is based on Robocorp certification exercises. While not production code, it follows good practices (clean repo structure, environment variables for secrets, no sensitive data committed).
This project is licensed under the MIT License.
MIT was chosen because it’s simple, permissive, and widely adopted in open-source.
It allows anyone to use, modify, and share the code freely, while keeping attribution and liability disclaimers clear.