Day 1 - Introduction to Automize Development
The goal is to understand the Automize development environment and record your first automation using the Automize Bot.
1. Understanding the Automize Platform
Automize is a no-code robotic process automation platform that allows anyone to build digital processes by simply recording their actions.
It bridges the gap between human tasks and system automation, enabling processes to run faster, more accurately, and 24/7.
At its core, Automize consists of two main components:
The Bot
A lightweight desktop agent that runs locally on your Windows 10 or 11 computer.
It records your interactions - such as clicks, keystrokes, and navigation - and can later play them back to repeat your work automatically.
The Bot also handles process debugging, and logs.
The Web Portal
A secure, cloud-based platform where you can view, edit, and manage your recorded processes.
Each recorded step is displayed as a process map, showing the top-down flow of your automation.
You can modify, rename, and connect activities, or add logic such as loops, decisions, and variables.
Key Concepts
| Term | Description | Example |
|---|---|---|
| Activity | A single action - such as a click, keystroke, or window open event. | Activity |
| Decision | A point where the flow of the process can take one of two or more alternative paths based on a specific condition. | |
| Trigger | A specific event or condition that initiates the process. | Trigger |
| Process | A sequence of activities / steps recorded by the bot. | |
| Sub process | A process contained within another process. It is best practice to reuse a process in other processes. | Sub process |
| Gateway | A branch in the process that determines the path the process will take based on specific conditions or events. Types of gateways are OR and AND. | |
| Connector | The visual link that defines the flow between two steps. There are 4 types of connectors, namely Default / True, False, Always and Exception. | |
| Variable | A value that changes during a process, like a name or amount. | {variable}, {invoice::line items} |
| Environment | Every process can be assigned as DEV, TEST, STAGING, or PRODUCTION to separate development and production versions. | |
| Formulas | An expression that performs calculations or manipulates data, similar to Excel formulas. | =ROUNDUP(AVERAGE(1, 2, 3, 4, 5, 6) + 10) |
Tip: Automize automatically optimises your process - merging related actions (like grouped keystrokes) and inserting logic (e.g., “wait for window” checks).
Also read Working with Process maps to obtain a visual representation of each of the above.
2. The Developer Workflow
Every Automize developer follows the same 3-step cycle:
Record - Use the Bot to capture the process exactly as you perform it.
Edit - Review and refine the process on the Automize web portal.
Test - Play the process back using the Bot to confirm that it runs smoothly.
This cycle repeats as you improve and optimise your automations.
Example: Record a simple action → review how the bot captured it → fix or rename steps → test it again until it runs perfectly.
3. Recording a Process
Let’s create your very first automation using a simple Windows app.
Objective
Record a process that opens the Windows Calculator, performs a basic calculation, and closes the app.
Requirements
For this exercise, the requirements are:
Windows 11 (or Windows 10)
Automize Bot installed and connected to your account
Automize Web Portal login access
Step-by-Step Exercise
Our exercise will focus in on recording a process of performing a calculation, using your built-in Calculator:
Open the Automize Bot on your computer.
Click the Record menu item on the left.
Click the Record button to begin capturing your actions.
Give your new process a name and press OK.
On your Windows taskbar, click in the Search box.
Write Calc in the search box.
Press Enter.
Use your mouse to perform a basic calculation - for example,
123 + 654 =.Close the Calculator.
Return to the Automize Bot and click Stop.
Log in to the Automize Web Portal.
Navigate to Library → Processes.
Open your newly recorded process.
Review the process map and ensure that:
Each activity (open app, click, type, close window) is listed.
The flow appears in the correct order.
No unnecessary actions were captured.
Go back to the Automize Bot, select the process, and click Play.
Watch as Automize repeats your recorded actions automatically!
Success Criteria: The Calculator opens, performs the same calculation, and closes - all without you touching the keyboard or mouse.
Optional Challenges
Try these to build confidence:
Challenge A – Open Notepad
Record a process that opens Notepad, types “Hello Automize!”, and closes the app.Challenge B – Multi-App Interaction
Record a process that opens Calculator, performs a calculation, then copies the result into Notepad.Challenge C – Add Wait Logic
After recording, edit your process to add a “wait for window” step before typing in Calculator.
4. Best Practices for Recording Processes
To get accurate, reliable recordings, follow these essential best practices before and during every recording session.
1. Keep Your Desktop Clean
Close all unnecessary applications, tabs, and windows.
Only keep open what is directly needed for your process.
A cluttered desktop increases the risk of incorrect element captures or selector mismatches.
2. Know the Process Before You Start
Write down the steps you intend to perform.
Ensure you know all input values (e.g., test data, login details, file paths).
Understand what success looks like - what should the bot achieve at the end?
- Avoid actions that do not directly add value to the process, i.e. Maximising windows, dragging windows, etc.
Example: “Open Calculator → add two numbers → close app.” Having a plan helps avoid unnecessary actions that clutter your process.
3. Work Smoothly and Avoid Distractions
Automize records the time between your steps to understand your pacing.
If you get distracted or pause too long, the bot will record that idle time as part of the process.
For the best results, complete the recording without interruptions.
Don’t check your phone or switch windows mid-recording - every click counts!
4. Minimise System Changes During Recording
Don’t move or resize windows after recording begins.
Pause OneDrive, as it might move files between OneDrive and your profile.
Keep your display layout consistent (screen resolution, scaling, etc.).
5. Use a Single Screen
Disconnect secondary monitors before recording.
The Bot records screen coordinates - multiple screens can cause misalignment or incorrect element selection.
Disconnect secondary monitors before recording.
The Bot records screen coordinates - multiple screens can cause misalignment or incorrect element selection.
6. Start and End in the Same State
Ensure that the process finishes with the same applications open as when it started.
If you opened Calculator, close it before ending the recording.
Consistent start and end states make automations repeatable and reliable.
Ensure that the process finishes with the same applications open as when it started.
If you opened Calculator, close it before ending the recording.
Consistent start and end states make automations repeatable and reliable.
7. Record on a Stable System
Pause Windows updates and notifications.
Ensure network connectivity is steady if your process uses web apps.
Disable pop-ups or auto-sleep modes during recording.
Pause Windows updates and notifications.
Ensure network connectivity is steady if your process uses web apps.
Disable pop-ups or auto-sleep modes during recording.
8. Follow Industry Best Practices
These are standard across major RPA platforms:
Small, focused processes: Record short, modular flows that are easy to maintain.
Naming consistency: Name activities and variables clearly (e.g.,
Open_Calculator,Enter_Value_A).Avoid hard-coding: Use variables instead of fixed paths or text values.
Reusable logic: If a pattern repeats, convert it into a sub-process.
Error resilience: Add “wait” and “exists” checks for unpredictable windows or pages.
Documentation: Describe the purpose of each process for future maintenance.
End of Day 1 Summary
By completing Day 1, you should now be able to:
✅ Explain the components of the Automize platform (Bot and Web Portal)
✅ Record a process using the Automize Bot
✅ View and review the recorded process on the website
✅ Play back the process successfully
✅ Apply best practices for reliable, consistent recordings
Next Step (Day 2):
Learn how to edit, interpret, and refine your recorded process using the Automize process map editor - adding logic, connectors, and basic conditions.
Next