studio-web
latest
false
- Getting started
- For administrators
- RPA workflow projects
- Creating an RPA workflow from an idea
- Creating a project
- How to start an RPA workflow
- Managing project files and folders
- Connecting RPA workflows to your accounts
- Configuring activities
- Managing the activities in a project
- Passing values between activities
- Iterating through items
- Managing the data in a project
- Configuring a project to use your data
- Using file and folder resources
- App projects
- Agentic processes
- Agents
- Solutions
- API workflows
- Tests
Studio Web user guide
Last updated Mar 9, 2026
Agentic process elements
Agentic processes use a distinct set of elements, which can be accessed from the left toolbar.
Elements are grouped under these categories:
- Tasks - Represent the building blocks of an agentic process. Tasks act as placeholders for actions or operations to be performed in the process.
- Gateways - Define decision points or control flow logic in a process, enabling conditional routing or parallel execution of automations.
- Events - Provide the ability to describe when something happens in a process. Events fall under three categories:
- Start events - Define how and when a process begins. They represent the entry point for a process.
- Intermediate events - Represent points within a process where specific actions pause the automation.
- End events - Mark the conclusion of a process path. Some end events represent visual markers, while others trigger specific actions.
- Subprocesses - Represent tasks that group related elements within a process to simplify the automation and improve readability.
- Data - Provide the ability to describe what information activities use or produce.
- Participant - Define an entity or role that is part of a collaboration.
Refer to the Maestro user guide for more details about each category of elements, as well as use cases and examples on how to best integrate these elements in your agentic process.