You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/reference/condition-builder.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ For the value you want to compare, you can write [expressions](../workflow/expre
14
14
#### Value prefix
15
15
This prefix is a convention used to indicate the data type of a value. It can be used to convert a value to the corresponding data type. For example, the "string::" prefix can be used to convert a value to a string type, and "number::" can be used to convert a value to a numeric type.
Learn more about Table on the [Table page](../workflow/table.md)
@@ -21,11 +21,11 @@ Learn more about Table on the [Table page](../workflow/table.md)
21
21
## Variables
22
22
You can add a variable from the variables page in the storage or from a workflow. Every time you want to assign or read the value of a variable, the variable name must start with a double dollar sign (`$$`). It's to differentiate between the storage variable and the workflow variable. For example, adding or updating a variable from a block.
Copy file name to clipboardExpand all lines: docs/reference/workflow-common-errors.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ Some common errors when running a workflow and how to solve it.
8
8
## Can't find an element with "{selector}" selector {#element-not-found}
9
9
This error happened because the element selector doesn't match with any elements on the page. For this case, you can check whether the elements exist on the page using the Element Exist block or enable the "Wait for selector" option in the element selector options.
10
10
11
-
11
+
12
12
13
13
## Can't find a tab with "{pattern}" patterns {#no-match-tab}
14
14
The Match Patterns you input don't match with any URLs tab. See how to write match patterns on the [MDN page](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Match_patterns#examples).
@@ -23,7 +23,7 @@ This happened because the block you're trying to use requires an active tab to w
23
23
24
24
To solve this, you can either use a [New Tab block](/blocks/new-tab.md) or an [Active Tab block](/blocks/active-tab.md) before the block you're trying to use.
Copy file name to clipboardExpand all lines: docs/workflow/debug-mode.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,17 +10,17 @@ And the debug mode is only available in the chromium version of Automa.
10
10
## Activate Debug Mode
11
11
There are two ways to activate the debug mode, the first is by going to the workflow settings, and the second is by going to the block settings. When you enable the debug mode in the workflow settings, Automa will use CDP API on the whole block.
And if you only want to use the debug mode in a specific block, you can enable it in the block settings.
16
16
17
17
## When to Use It
18
18
You can use the debug mode when you want to type text on a website, but the text field uses a WYSIWYG editor, for example, typing a tweet in the editor or writing a message in Discord using the [Forms block](../blocks/forms.md).
and the [Get Text block](/blocks/get-text.md) using `.text` as the element selector, and the website [DOM tree](https://en.wikipedia.org/wiki/Document_Object_Model).
28
28
@@ -55,11 +55,11 @@ Automa Element Selector
55
55
56
56
In the Automa Dashboard, click the <v-remixiconname="riFocus3Line" /> button on the sidebar, And Automa will inject an element picker into the current page. You can click or press the `Space` key to select an element. It will automatically generate a selector for the selected element.
And you'll find the "Select an element" button when editing a block. When you click it, it will inject the element picker to the current page, select an element, and click the "Select element" button in the element picker.
61
61
62
-
62
+
63
63
64
64
## Custom Selector Syntax
65
65
Besides supporting the standard [CSS Selector](https://www.w3.org/TR/selectors-4/) and XPath expression, Automa supports a non-standard syntax:
But what if you want to use the `url` property on the first element of the array as a value inside the [New Tab block](../blocks/new-tab.md) URL? For that, use the following expression:
`0` on that expression means the first element of the array. And if you want to get the second element of the array, replace it with `1`. `2` for the third element; `3` for the fourth element; and so on.
52
52
@@ -336,7 +336,7 @@ Only supported in the chromium based browser
336
336
337
337
Automa also supports javascript within the expression, but to write a javascript, you must add `!!` characters as the first value on a text field of a block. For example, from <codev-pre>The number is: {{variables.number}}</code> to <codev-pre>!!The number is: {{variables.number}}</code>.
Copy file name to clipboardExpand all lines: docs/workflow/global-data.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,4 +14,4 @@ For example, you have multiple new tab blocks wherein the URL input has the same
14
14
```
15
15
And access the global data inside the URL text field of the New Tab block using an [expression](./expressions.md). For example, <codev-pre>{{globalData.url}}</code>
Copy file name to clipboardExpand all lines: docs/workflow/looping.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,20 +16,20 @@ Looping is helpful when you want to process multiple similar items, for example
16
16
17
17
When using the [Loop Data](../blocks/log-data.md) or [Loop Elements block](../blocks/loop-elements.md), the [Loop Breakpoint](../blocks/loop-breakpoint.md) must include in the workflow. The Loop Breakpoint is for telling the workflow where the scope of the loop is. And inside the Loop Breakpoint, you also must input the Loop id of the loop block.
18
18
19
-
19
+
20
20
21
21
The above workflow will repeatedly execute the Forms and the Get Text block based on the numbers of the items. And after it loops all the items, the workflow will continue to the Export Data block.
22
22
23
23
And when you're not defining the loop scope using the Loop Breakpoint block, the looping will not work.
24
24
25
-
25
+
26
26
27
27
The above will execute the Forms and the Get Text block once and then continue to the Export Data block.
28
28
29
29
### Access Loop Item
30
30
You can use [expressions](./expressions.md) to access data from the current loop iteration inside the loop scope. For example, <codev-pre>{{loopData.loopId}}</code>; replace the `loopId` with the Loop id you inputted inside the Loop Data or Loop Element block.
The <codev-pre>{{loopData.loopId}}</code> expression will return:
35
35
```json
@@ -44,6 +44,6 @@ So if you want to access the index of the loop, you can use [expressions](./expr
44
44
45
45
Using the [Repeat Task block](../blocks/repeat-task.md) is the easiest way to do looping. You only need to define how many times to repeat the actions and where to start to repeat them.
The above will start to repeat to execute from the Click Element block, and after it executes three times. The workflow will continue to the New Tab block.
These parameters will be inserted as [variables](./variables.md) in the workflow, and the variable name the same as the parameter name. For example, you can access the value of the `keyword` parameter like <codev-pre>{{ variables.keyword }}</code>
0 commit comments