Documentation

Getting Started with OTTO

The Otto application is designed to:

  • Run custom web automations on a web server or your local machine.
  • Save time and increase productivity by automating repetitive work so you can focus on doing the work you enjoy.
  • Run automations against multiple data entries.

Lets get started designing your first workflow!

First, download the free Google chrome extension.

Creating a Workflow

To get started go to dyno-ai.com/otto.

Lets add the first workflow by clicking Add Workflow.

To edit an existing workflow:

  • Click the gray pen icon next to the workflow name.
  • Refresh the workflow by clicking the refresh button next to the Add Workflow button.

This will create a new widget that you can customize.

What is a widget?

A widget is a representation of a user action. You can looks at it as telling your computer what to do. Each command is simplified allowing you to string a series of commands together creating a workflow.

Each widget needs to be given a name, automation type, action as well as the necessary input for the action to be processed.

*developer notes: more automation types and actions are in development.

When all necessary fields are completed, click ‘Submit’ to save the widget details.

Widget Actions

Widget actions are the commands to give to the computer.

These commands define the action that should be taken in the workflow.

GoToUrl : Go to a specified website. Requires: url

Click: Click a selector on the page. Requires: selector.

Type: Fill in an input field. Requires: selector to type in. Copy – what to type.

GetText: Retrieve the text in an element. Requires: selector.

GetLink: Retrieves the link/ href of an element. Requires: selector.

KeyboardEnter: Simulates clicking ‘enter’ on the keyboard.

GoBack: Go back to the previous page.

SelectOption: Selects an option from a drop down or any type of selection where options are provided.

* notes: More actions are in development

Key Terms

  • Selector: An element identifier such as id or class eg #elementId, .class, [id=”element”], etc. (read more on Webflow).
  • Element: This represents an HTML component on the page (read more on W3 Schools).
  • Here is an article on how to find an element or selector on a webpage – link.
  • Url: This is simply the website address.

Note: always use double quotes ” instead of single quotes ‘ for consistency.

After your workflow is complete click ‘Save’.

Minimum widget entries required is two.

If the workflow is saved successfully it will appear under the workflow column.

Components

Workflow: The workflow name.

Parameters*: Parameters for server-side automations. More information below.

Red button: Delete workflow.

Green button: Upload data for server-side automations.

Blue button: Run automation on your computer.

Gray pen icon: Edit a workflow.

Automation Types

Local Automations

These run on the users computers. The automation will create a new tab on the browser and execute the commands. When creating the automation, parameters are not required.

Local automations are best for daily tasks, automation that requires login, or repetitive forms.

Server-Side Automations

These runs on our secure servers. These are for bulk automation. For example, processes that need to be repeated for a large amount of data. These automations require parameters.

What are Parameters?

For server-side automations, the user will need to upload a csv file. The row on this file will be mapped to the parameter on the widget. Parameters are placeholders or variables representing an entry on the uploaded csv document. On the widget, parameters are represented with & symbol. eg: &firstname

Note: Local automations do not support parameters and server-side automations require parameters.

It is best to test your automation locally, then parametrize the variables for server-side.