RGO (Robogator Original) certified ready-made automation tasks are subject to the following standards

Last updated: May 2026

What are RGO certified automation tasks

To clarify, an RGO certified ready-made automation task is a collection of Robogator tasks grouped under a Robogator account, available to import with the right license plan from the Robogator cosmos and ready to hit and run immediately after download without any technical error.

Cosmos ready-made automation tasks manifest

  1. Seamless start: Download and run the automation tasks without initial configuration by using a default setup.
  2. Rich description: Detailed description of the automation tasks.
  3. Comprehensible console information: See what works and what doesn't in a way that is recognizable so you can understand it even years from now.
  4. Comprehensive error handling: Run the automation tasks without uncertainties.
  5. Fun to use: The RGO certified ready-made automation tasks should bring a smile to your face when you use it.

Guideline

The following standards and restrictions for published ready-made automation tasks available on Robogator cosmos are intended to meet the high requirements for end-user usability and to lower the initial barriers for a smooth and pleasant interaction with the Robogator platform.

Account title

Make the account title short and sweet. The title should start with a uppercase letter and be nice and human readable. Here are some examples:

  • Desktop cleaner
  • Data migration tools
  • Password generator

Account image

Select a colorful and relatable image for the automation task account. The main reason for the account image is to have another quick recognition feature to better recognize ready-made automation tasks on the fly in the deep end of the Robogator cosmos.

Task title

The task title should describe the whole function of the task in a few words, also should start with a uppercase letter an be nice and human readable. Here are a few examples:

  • Cleans desktop and stores data in archive folder
  • Classify files
  • Generate a random 32 character string

Task description

For each task, write a clear and simple description that explains exactly what the task is doing. The minimum requirement is 150 characters. Some examples:

  • This task does a desktop cleanup and stores files in an archive desktop folder by cleanup date and time. It is possible to exclude files or directories from the desktop cleanup
  • Reads a csv file and lists every unique value and calculates how many times each value appears in your selected csv column. It does this using the column header name of the given csv file and writes the result to a newly created csv structured file.

Task parameters

Use PascalCase parameter names that start with an uppercase letter. Exampels are:

  • SourcePath
  • DbConnectionType
  • Url

Each task must run without any parameter input. This requires default values if needed in the script for each parameter available in the task.

The paramtere description must be at least 25 characters long.

In the script's header, add a commented-out line for each parameter, using the following structure:

  • <param>"Parameter name","Default value","Parameter description"</param>

Some valid examples are:

  • <param>"PathToFile","..\Local\Temp\TaskUuid","Set the path to the file without the filename itself"</param>
  • <param>"FileName","","Output csv filename e. g. my_data.csv"</param>
  • <param>"Amount","0","specify the number of repetitions"</param>

Using keys

Use PascalCase key names that start with an uppercase letter. Except if you are going to use the first available key for the task feature. Exampels are:

  • MapServiceV1ApiToken
  • XCorePowerAdmin
  • SftpPrivateKey (keyDefaultFirst)

Choose a long, task-related key name. This will help prevent keys with similar names in the Robogator key tab. This makes it easier to understand the keys and their belonging.

If you want to use the first available key for the task, use the keyDefaultFirst feature. In that case, the key description should be the key name followed by (keyDefaultFirst), e.g., SftpPrivateKey (keyDefaultFirst). Then, if auto-key-generation on import is enabled (the default), a key named SftpPrivateKey will be created, or linked if a key with that name already exists. This feature can be turned off if needed.

It is necessary to set auto-generated-during-account-import-by-robogator as the default password. This improves the user experience and prevents technical errors.

Every script that uses keys must check for this default password and message the user to replace it with a proper one before the task can run.

The key description must be at least 25 characters long.

In the script's header, add a commented-out line for each key, using the following structure:

  • <key>"Key name","Key description"</key>

Here are a few good ones:

  • <key>"ApiTokenForServiceXY","Add the token for the api with the key name ApiTokenForServiceXY"</key>
  • <key>"UserPw","Store the user password in an key named Password and add it to the task"</key>
  • <key>"SftpPrivateKey (keyDefaultFirst)","The first key added to the task is the one that gets used. The key name can be chosen freely. By default, a key called SftpPrivateKey is created, or linked if a key with that name already exists"</key>

Using followed tasks

Only use followed by links to tasks within the account. Followed by task links are getting automatically detected and displayed in the associated cosmos ready-made automation task overview. No manual intervention is required.

Task tags

Use short and meaningful tags, single words or phrases, to best describe the task, the technology used in the task, and the target field for the task usage. Exampels are:

  • Multithreading
  • Delete folder
  • Write text file

Try to check the already existing tags and reuse them from the Robogator cosmos to reduce multiple variations of the same tag.

For each task, define at least one tag, ideally the most descriptive one. Add these tags as a commented-out collection in the script's header, using the following structure:

  • <tags>"tag1"</tag>

Here are some good examples:

  • <tags>"Crawler","Folder names","Csv output"</tags>
  • <tags>"Desktop cleaner"</tags>
  • <tags>"Csv","Big data","Multithreading"</tags>

Task chat messages

Use Robogator chat messages (Write to Console) to notify the user about the most important stuff. Use clickable links and bold text to maximize the user experience. The script must start with an initial message. Keep in mind that too many messages will slow down the script.

Task license check

After the initial message, every Task must verify that the required License Plan is active. If the required License Plan is missing or inactive, the user must be notified that a valid license is required to use the Task's full features. This prevents misinterpretation of results caused by running scripts without a valid License Plan.

Task cancellation

Each task must be able to be cancelled immediately. If necessary, add manual cancellation steps to the script to ensure the desired behavior.

Task error handling

Please note this carefully. Ensure that sufficient error handling fallback routes are included in the task script. The goal is to present only informative soft errors to the end user.